Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-11 Thread Marshal Linfoot
Great news Jim. Gonna try it out as soon as I get home.

Thanks!

On 8/11/10, Jim Gay j...@saturnflyer.com wrote:
 I've made some updates and I'm not able to recreate this problem.

 I've created a new instance from edge
 Used the #4 template (Styled Blog)
 Copied the Styles.css page content into a new stylesheet and saved it.
 Changed the layout from using a direct link to the /styles.css page to
 r:stylesheet slug=styles.css as=link / (Using the same slug as the
 existing page)
 Reload the public view and see everything as it should be.

 On Tue, Aug 10, 2010 at 4:58 PM, kbingman kbing...@gmail.com wrote:

 Marshal,

 there are a couple of pages set up in the database for CSS, one for
 CSS in general, then child pages for each actual CSS. When I took a
 look, the status was set to 90, which is pending. Hopefully Jim will
 have this sorted out soon (or already).

 Keith

 On Aug 5, 6:18 pm, Marshal Linfoot mlinf...@gmail.com wrote:
  Keith, how did you determine that the stylesheet was in draft status? I
  browsed my sqlite database looking for that and couldn't find the
 styesheet
  page anywhere.
 
  On Thu, Aug 5, 2010 at 5:23 AM, kbingman kbing...@gmail.com wrote:
   Jim,
 
   looks like there is a little bug here... the stylesheet is set to
   draft after it is created. At least is was for me, which is probably
   was Marshal is not getting it in his layout.
 
   Keith
 
   --
 
  marshal




 --
 Jim Gay
 Saturn Flyer LLC
 http://www.saturnflyer.com
 571-403-0338


-- 
Sent from my mobile device

marshal


[Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-03 Thread Jim Gay
I've added a new feature to the core. Read about it here
http://radiantcms.org/blog/archives/2010/08/03/manage-css-and-javascript-from-the-admin-ui/

Radiant now has features like the SNS extension provided, but better.

-- 
Jim Gay
Saturn Flyer LLC
http://www.saturnflyer.com
571-403-0338


[Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-03 Thread Jim Gay
I've added a new feature to the core. Read about it here
http://radiantcms.org/blog/archives/2010/08/03/manage-css-and-javascript-from-the-admin-ui/

Radiant now has features like the SNS extension provided, but better.

-- 
Jim Gay
Saturn Flyer LLC
http://www.saturnflyer.com
571-403-0338


Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-03 Thread Marshal Linfoot
Jim, I've used the sns extensions for some time now and, from a
non-developer perspective, am happy to see the functionality moved into
core. I'm sure developers will find it easier to work with, too.

I gave it a try on a test server that had sns, sns_page_hooks, sns_minifier,
sns_sass_filter already installed. Here are the steps I took:

1. rake radiant:freeze:edge
2. rake radiant:update
3. rake production db:migrate
4. removed all the sns* extensions with script/extensions uninstall sns
(for each extension)
5. rake radiant:update
6. rake production db:migrate:extensions
7. started the server and uploaded my css to the new stylesheets page
8. changed the stylesheet tag to read r:stylesheet slug=main as=link
media=screen / in the layout
9. and for good measure, restarted the server

When I open the home page of the test site, the css is not applied. Viewing
the page source I see:

link rel=stylesheet type=text/css href=/css/main?1280848729
media=screen /

Typing either localhost:3000/css/main?1280848729 or
localhost:3000/css/main in the browser URL field produces the same Page
Not Found result.

Have I missed some important step? Any ideas?

I haven't tried it on a clean, new radiant instance without any other
extensions yet.

Lastly, will you be adding the ability to minify the css/javascript like
sns_minifier?


-- 
marshal


Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-03 Thread Jim Gay
On Tue, Aug 3, 2010 at 12:01 PM, Marshal Linfoot mlinf...@gmail.com wrote:

 Jim, I've used the sns extensions for some time now and, from a
 non-developer perspective, am happy to see the functionality moved into
 core. I'm sure developers will find it easier to work with, too.

 I gave it a try on a test server that had sns, sns_page_hooks,
 sns_minifier, sns_sass_filter already installed. Here are the steps I took:

 1. rake radiant:freeze:edge
 2. rake radiant:update
 3. rake production db:migrate
 4. removed all the sns* extensions with script/extensions uninstall sns
 (for each extension)
 5. rake radiant:update
 6. rake production db:migrate:extensions
 7. started the server and uploaded my css to the new stylesheets page
 8. changed the stylesheet tag to read r:stylesheet slug=main as=link
 media=screen / in the layout
 9. and for good measure, restarted the server

 When I open the home page of the test site, the css is not applied. Viewing
 the page source I see:

 link rel=stylesheet type=text/css href=/css/main?1280848729
 media=screen /

 Typing either localhost:3000/css/main?1280848729 or
 localhost:3000/css/main in the browser URL field produces the same Page
 Not Found result.

 Have I missed some important step? Any ideas?

 I haven't tried it on a clean, new radiant instance without any other
 extensions yet.

 Lastly, will you be adding the ability to minify the css/javascript like
 sns_minifier?


 --
 marshal


Thanks very much for testing this out, Marshal.

The part you missed is that there was no conversion of content from the SNS
records in the database to StylesheetPages and JavascriptPages.

SNS stores content in a text_asset table, but none of the steps you did
moved that content.

I haven't yet created the necessary migrations, but judging from your
experience here it looks like you'd assume that a migration would do the
trick. So I'll probably just add migrations to move the content from within
the Sheets extension.

And if you are moving from SNS, I've also allowed for the name attribute
to work. So your r:stylesheet name=main / will still work, no need to
update to be a slug attribute instead.



-- 
Jim Gay
Saturn Flyer LLC
http://www.saturnflyer.com
571-403-0338


Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-03 Thread Marshal Linfoot

 Thanks very much for testing this out, Marshal.


Happy to help in any small way.

The part you missed is that there was no conversion of content from the SNS
 records in the database to StylesheetPages and JavascriptPages.


I wasn't expecting the old sns content to be moved. Instead, I let the
uninstall remove it (at least I thought that's what would happen) and then I
created a new Sheets/stylesheet page and copied the css into it from a local
text file.

SNS stores content in a text_asset table, but none of the steps you did
 moved that content.


Did the uninstall remove it?


 I haven't yet created the necessary migrations, but judging from your
 experience here it looks like you'd assume that a migration would do the
 trick. So I'll probably just add migrations to move the content from within
 the Sheets extension.


This would be great!


 And if you are moving from SNS, I've also allowed for the name attribute
 to work. So your r:stylesheet name=main / will still work, no need to
 update to be a slug attribute instead.


I had the name attribute at first, but when the css wasn't applied I
changed it to slug  thinking that might be the problem.

-- 
 Jim Gay
 Saturn Flyer LLC
 http://www.saturnflyer.com
 571-403-0338


PS. Minify?

-- 
marshal


Re: [Radiant] New feature: manage CSS and Javascripts from the Admin UI

2010-08-03 Thread Marshal Linfoot
Jim, I just now tried this on a fresh Radiant instance.

I installed the Styled Blog so I would have some content and css to
work with. Cut and pasted the css from Styles/css into
Design/Stylesheets/main and then deleted the Styles page (original css
gone, copy of the original css in /css/main). Updated the layout to
use Sheets, ie r:stylesheet name=main as=link /. The radius tag
renders as expected
link rel=stylesheet type=text/css href=/css/main?1280863253 /,
but the page is not styled.

Can't see that I've missed anything. Could it be a caching issue, that
something is pointing to the old, non-existent css?
--
marshal