Hi!
As of today, I can't change template in my 2.2.2 installation. When I try, the template name changes and stays, but the page itself displays the default template. I've tried with different templates and pages, cleared my cache and banged my head to my desk but nothing seems to work.
Yesterday it worked just fine.
With a quick search I found ppl with a bit similar problems and the suggested solution was that MySql timezone should match with date.timezone in php.ini. However, when I view php info, date.timezone has "no value".
Thanks.
Fixing the date/timezone would probably fix it. In the meantime, you can right-click on the resource and select QuickUpdate. That should let you set the template, though you definitely want to follow the advice in the other threads to fix the date/timezone.
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
QuickUpdate didn't work either. How can I find out my MySQL timezone and how can I edit php.ini's date.timezone?
These might help:
https://forums.modx.com/index.php?topic=43047.0
http://tracker.modx.com/issues/6931
------------------------------------------------------------------------------------------
PLEASE, PLEASE specify the version of MODX you are using.
MODX info for everyone:
http://bobsguides.com/modx.html
Thanks man, I truly appreciate the help - you were quick to answer my last issue too. Are you hired by ModX or just an enthusiast? Either way, ppl like you make ModX rock.
Template issue just got a bit more weird. Earlier when I tried to change templates it didn't work. Now one of the pages has the new template but I can't change it back. It's as if the template changes had a delay.
I'll try the timezone fixes first.
Also getting internal server errors and any content entered to a page under my second context doesn't show. Can this still be the timezone issue?
-
☆ A M B ☆
- 3,141 Posts
Doesn't sound like anything familiar... server errors aren't good, and usually have more information in a server error log - I suggest checking that, as it may have some leads as what's happening.
Did you also check the MODX error log which can be found under Reports?
Here's my ModX error log:
[2012-05-21 14:30:50] (ERROR @ /index.php) `id` is not a valid integer and may not be passed to makeUrl()
[2012-05-21 14:30:59] (ERROR @ /index.php) `id` is not a valid integer and may not be passed to makeUrl()
[2012-05-21 15:05:52] (ERROR @ /connectors/element/index.php) Error caching lexicon topic lexicon/en/core/default
[2012-05-21 15:43:43] (ERROR @ /connectors/layout/modx.config.js.php) Error caching lexicon topic lexicon/en/core/resource
[2012-05-21 15:46:11] (ERROR @ /connectors/element/propertyset.php) Error caching action map mgr/actions
[2012-05-21 15:49:17] (ERROR @ /connectors/element/propertyset.php) Error caching action map mgr/actions
[2012-05-21 15:49:39] (ERROR @ /connectors/element/propertyset.php) Error caching action map mgr/actions
[2012-05-21 15:49:39] (ERROR @ /connectors/element/propertyset.php) Error caching lexicon topic lexicon/en/core/element
[2012-05-21 16:08:41] (ERROR @ /connectors/element/index.php) Error caching action map mgr/actions
[2012-05-22 08:59:20] (ERROR @ /connectors/element/tv/renders.php) Error caching lexicon topic lexicon/en/core/tv_input_types
[2012-05-22 09:02:31] (ERROR @ /connectors/element/propertyset.php) Error caching lexicon topic lexicon/en/core/default
[2012-05-22 09:02:31] (ERROR @ /connectors/element/index.php) Error caching action map mgr/actions
[2012-05-22 09:02:31] (ERROR @ /connectors/element/propertyset.php) Error caching lexicon topic lexicon/en/core/element
[2012-05-22 09:04:03] (ERROR @ /connectors/element/propertyset.php) Error caching lexicon topic lexicon/en/core/default
[2012-05-22 09:04:03] (ERROR @ /connectors/element/propertyset.php) Error caching action map mgr/actions
[2012-05-22 09:56:13] (ERROR @ /connectors/element/propertyset.php) Error caching action map mgr/actions
I decided to circumvent the problem and instead of using a second context, used a container for English version of the site. After all it's a pretty small website and I only have three templates. Client won't be changing them anyways.
My gut tells me that this has something to do with the host's settings. I've never used this host before and probably never will again. Nothing similar has ever happened with the ones I normally use.
Could be the permissions or ownership of the core/cache dir.
Also, a plugin or snippet has 'id' in quotes where it shouldn't be.