Re: [Radiant] Missing Layout in the Admin
Everything is owned as it should be, and I can't see anything out of the ordinary otherwise. Any other ideas? On 29 March 2010 18:17, Andrew Gehring andrew.gehr...@gmail.com wrote: I've had this happen due to ownership/permission issues... (e.g.; not owned by www-data on ubuntu) Andrew On 3/29/10, Neil Middleton n...@monochrome.co.uk wrote: I have a site in production that has suddenly lost the layout for the admin pages. I've tried blipping the webserver and vendoring Radiant into the codebase. However, nothing seems to be fixing it, and nothing is showing up in any of the logs. Any ideas? -- Neil Middleton ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org -- Sent from my mobile device ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org -- Neil Middleton Technical Lead Monochrome Ltd Tel: +44(0)845 202 0085 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Missing Layout in the Admin
OK, I've tracked this down to a statement in my production.rb: SiteController.cache_timeout = 12.hours Which raises the question - what is the correct way of overriding the caching time, and why should this affect the template rendering in the admin? N On 30 March 2010 11:02, Neil Middleton n...@monochrome.co.uk wrote: Everything is owned as it should be, and I can't see anything out of the ordinary otherwise. Any other ideas? On 29 March 2010 18:17, Andrew Gehring andrew.gehr...@gmail.com wrote: I've had this happen due to ownership/permission issues... (e.g.; not owned by www-data on ubuntu) Andrew On 3/29/10, Neil Middleton n...@monochrome.co.uk wrote: I have a site in production that has suddenly lost the layout for the admin pages. I've tried blipping the webserver and vendoring Radiant into the codebase. However, nothing seems to be fixing it, and nothing is showing up in any of the logs. Any ideas? -- Neil Middleton ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org -- Sent from my mobile device ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org -- Neil Middleton Technical Lead Monochrome Ltd Tel: +44(0)845 202 0085 -- Neil Middleton Technical Lead Monochrome Ltd Tel: +44(0)845 202 0085 ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Reorder Extension testing issues
BTW, if any are curious, here's what I think I know about this (sorry, forgot to report back about the experiments): rake spec or rake spec:models load *only* the base radiant db migrations into the test database -- they load no extension migrations at all. This means that if any extension modifies the base tables in its migrations, those migrations are not loaded during this test. The only time any extension migrations get loaded into the test db is under rake spec:extensions when they do get loaded, when the tests are run for that particular extension. (This may not be entirely correct, as I realized as I wrote the above I didn't have any integration tests in my local tree involving reorder, and those might have caused the reorder migrations to load.) Since the reorder extension modifies children_find_options (replacing 'published_at' with 'position' as the default) it breaks the tests, as the position column migration has not been loaded when the model tests are being run. If it had simply created a position column and not altered default behavior (merely giving you the additional option of using by=position') the errors would not have appeared, and my confusion would have been less. BTW, am I right in assuming there isn't a command to test a specific extension, only one which tests all installed extensions at once? Have Fun, Arlen -- In God we trust, all others must supply data ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Reorder Extension testing issues
On Tue, Mar 30, 2010 at 9:53 AM, Arlen Walker arlen.wal...@gmail.com wrote: BTW, am I right in assuming there isn't a command to test a specific extension, only one which tests all installed extensions at once? rake spec:extensions EXT=ext_name ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
Re: [Radiant] Reorder Extension testing issues (Final Solution)
On Mar 30, 2010, at 12:33 PM, john muhl wrote: On Tue, Mar 30, 2010 at 9:53 AM, Arlen Walker arlen.wal...@gmail.com wrote: BTW, am I right in assuming there isn't a command to test a specific extension, only one which tests all installed extensions at once? rake spec:extensions EXT=ext_name Ah, thank you. BTW, have a solution to this issue, finally. Radiant is not updating the schema.rb file when extensions are migrated. After doing an extension migration use: rake db:schema:dump to update the schema.rb file. Then the test db will be recreated properly during testing. So much simpler when I finally realized 'rake spec' was using schema:load and not remigrating everything every time. (What can I say? I've been sick so my mind has been slower than usual.) Radiant needs to do a schema:dump after the extension migrations happen, but until then, doing it manually seems to work. Have Fun, Arlen -- In God we trust, all others must supply data ___ Radiant mailing list Post: Radiant@radiantcms.org Search: http://radiantcms.org/mailing-list/search/ List Site: http://lists.radiantcms.org/mailman/listinfo/radiant Radiant: http://radiantcms.org Extensions: http://ext.radiantcms.org
