Evolution 1.0.7 - MODX Community Forums https://forums.modx.com/board/?board=276 <![CDATA[Upgraded to 1.7 and can't login]]> https://forums.modx.com/thread/82365/upgraded-to-1-7-and-can-t-login#dis-post-458872
I trying to upgrade from 1.2 to 1.7 or 1.8 and when I get the upgrade it will not allow me to log into the CMS... any ideas to why this is occurring would be great.

Thanks]]>
https://forums.modx.com/thread/82365/upgraded-to-1-7-and-can-t-login#dis-post-458872 Fri, 15 Mar 2013 09:10:59 +0000 https://forums.modx.com/thread/82365/upgraded-to-1-7-and-can-t-login#dis-post-458872
<![CDATA[503 Site Unavailable?]]> https://forums.modx.com/thread/83155/503-site-unavailable#dis-post-458788
Site cache & browser cache has also been cleared.]]>
https://forums.modx.com/thread/83155/503-site-unavailable#dis-post-458788 Thu, 14 Mar 2013 05:34:16 +0000 https://forums.modx.com/thread/83155/503-site-unavailable#dis-post-458788
<![CDATA[MODx Parse Error]]> https://forums.modx.com/thread/83120/modx-parse-error#dis-post-458615 everything installed ok but when i try to preview the example homepage i get this message:


« MODx Parse Error »

MODx encountered the following error while attempting to parse the requested resource:
« PHP Parse Error »
 
PHP error debug
  Error:	set_time_limit(): Cannot set time limit due to system policy	 
  Error type/ Nr.:	Warning - 2	 
  File:	/customers/4/8/d/creatingstories.co.uk/httpd.www/assets/snippets/ajaxSearch/classes/ajaxSearch.class.inc.php	 
  Line:	78	 
  Line 78 source:	 set_time_limit($asCfg->cfg['timeLimit']);	 
 
Parser timing
  MySQL:	0.0032 s	(1 Requests)
  PHP:	0.0160 s	 
  Total:	0.0192 s




I have no idea where to start to get things running, the site is hosted on www.one.com, let me know the info you need to help and i'll ask support for it, can can say this much though, no ssh access or unzipping supported sad

]]>
https://forums.modx.com/thread/83120/modx-parse-error#dis-post-458615 Wed, 13 Mar 2013 07:05:38 +0000 https://forums.modx.com/thread/83120/modx-parse-error#dis-post-458615
<![CDATA[Moving the site to a new hosting server, site is ok, but cannot login to manager]]> https://forums.modx.com/thread/81327/moving-the-site-to-a-new-hosting-server-site-is-ok-but-cannot-login-to-manager?page=2#dis-post-448424 I was forced to move a productive site to a new hoster because the old one did not switch magic-quotes-settings to off. I moved the files, dumped the mysql database and imported it do the new server, adapted the config.inc.php file. The site is running under a temporary url because i did not switch the dns server address til now.

When I try to log in to the manager the login page of the old server shows up, i cannot login to the temporary url. Is it because it didn't change the dns server address til now? Or is something else that i have to change? Same with install by the way, i cannot do an upgrade install, the old server address shows up.

Thanks for helping.
Markus]]>
https://forums.modx.com/thread/81327/moving-the-site-to-a-new-hosting-server-site-is-ok-but-cannot-login-to-manager?page=2#dis-post-448424 Thu, 27 Dec 2012 09:45:53 +0000 https://forums.modx.com/thread/81327/moving-the-site-to-a-new-hosting-server-site-is-ok-but-cannot-login-to-manager?page=2#dis-post-448424
<![CDATA[How to set magic-quotes_gpc to off when hosting provider will not set it off?]]> https://forums.modx.com/thread/81292/how-to-set-magic-quotes-gpc-to-off-when-hosting-provider-will-not-set-it-off#dis-post-448117 I am running a website at a swiss hosting provider. The provider updated php-Version to 5.3.16 and set the magic-quotes_gpc setting to on. They will not set it to off and will not downgrade to Version 5.2.

The hosted website uses MaxiGallery and now there is backslahes all over!! My client needs MaxiGallery to put on a new auction soon. Is there any way to trick the hosting provider and set the setting to off?

Thanks for helping me.
Markus]]>
https://forums.modx.com/thread/81292/how-to-set-magic-quotes-gpc-to-off-when-hosting-provider-will-not-set-it-off#dis-post-448117 Sun, 23 Dec 2012 12:16:26 +0000 https://forums.modx.com/thread/81292/how-to-set-magic-quotes-gpc-to-off-when-hosting-provider-will-not-set-it-off#dis-post-448117
<![CDATA[webuser vs manageruser conflict after upgrade 1.0.7]]> https://forums.modx.com/thread/81234/webuser-vs-manageruser-conflict-after-upgrade-1-0-7#dis-post-447827
Because the Web User Groups and Manage User Groups conflict for your role this Resource will be public. Contact a site administrartor for futher help.

This occured after the upgrade to 1.0.7. When I assign a superuser role to the user, the error goes, but when he/she tries to edit a resource, there are no tabs (general,settings,access permision) And no fields, like title, longtitle etc. So nothing to edit. In the role of admin there s no problem.]]>
https://forums.modx.com/thread/81234/webuser-vs-manageruser-conflict-after-upgrade-1-0-7#dis-post-447827 Thu, 20 Dec 2012 04:09:37 +0000 https://forums.modx.com/thread/81234/webuser-vs-manageruser-conflict-after-upgrade-1-0-7#dis-post-447827
<![CDATA[system events from 1970?]]> https://forums.modx.com/thread/81209/system-events-from-1970#dis-post-447570 Check the image]]> https://forums.modx.com/thread/81209/system-events-from-1970#dis-post-447570 Tue, 18 Dec 2012 03:30:39 +0000 https://forums.modx.com/thread/81209/system-events-from-1970#dis-post-447570 <![CDATA[PHP Server Upgrade Forced MODX Upgrade and now it's full of errors]]> https://forums.modx.com/thread/81120/php-server-upgrade-forced-modx-upgrade-and-now-it-s-full-of-errors#dis-post-446949
Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in rss.inc.php on line 50

Strict Standards: strftime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in document.parser.class.inc.php on line 1826

Strict Standards: strtotime(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected 'America/New_York' for 'EST/-5.0/no DST' instead in rss.inc.php on line 50.... etc. you get the picture


I don't know what any of this is talking about, or why it happened, or how to fix it. Why would a PHP upgrade break the entire site? How do I fix this "timezone" issue?]]>
https://forums.modx.com/thread/81120/php-server-upgrade-forced-modx-upgrade-and-now-it-s-full-of-errors#dis-post-446949 Wed, 12 Dec 2012 08:18:05 +0000 https://forums.modx.com/thread/81120/php-server-upgrade-forced-modx-upgrade-and-now-it-s-full-of-errors#dis-post-446949
<![CDATA[After blocking forgot manager password plugin exploit -- change passwords?]]> https://forums.modx.com/thread/80768/after-blocking-forgot-manager-password-plugin-exploit----change-passwords#dis-post-446883
Earlier today, I disabled the forgot manager password plugin as in immediate-response action for impacted sites -- quite a few -- I've installed, per solution #1 in http://forums.modx.com/thread/80701/modx-evolution-1-0-6-and-prior-unauthorized-manager-access#dis-post-444667.

As I read it, I've closed the door on this exploit. Question becomes if exploit had theoretically been used in the (~48 hours) since announcement of 1.0.7, and could continue to be used post "door closing" via a manager password acquisition in the exploit.

Thinking through possible exploits, I'm operating on the assumption that any exploit allowing access wouldn't reveal/provide manager passwords to an attacker other than through a hypothetical password reset / change.

So... If I'm able to login with an existing manager password (to turn off the plugin), does it means that an exploit didn't result in a password change, and thus, can I assume that there's no need to change the password? If it was only one site / password for me only, I'd just change it, but as there quite a few people who would be impacted by mass password changes, as they say, "inquiring mind wants to know".

Thanks in advance

]]>
https://forums.modx.com/thread/80768/after-blocking-forgot-manager-password-plugin-exploit----change-passwords#dis-post-446883 Wed, 12 Dec 2012 11:09:01 +0000 https://forums.modx.com/thread/80768/after-blocking-forgot-manager-password-plugin-exploit----change-passwords#dis-post-446883
<![CDATA[PHP 5.4.X-Support]]> https://forums.modx.com/thread/80868/php-5-4-x-support#dis-post-446441
this is only a short question: is PHP 5.4.x support already included or do we have to change the scripts like described on that link here?
http://tracker.modx.com/issues/7300
(Sorry, if that already has been mentioned somewhere. Couldn't find it on the forum.)

Thanks in advance & greetings]]>
https://forums.modx.com/thread/80868/php-5-4-x-support#dis-post-446441 Mon, 10 Dec 2012 12:47:13 +0000 https://forums.modx.com/thread/80868/php-5-4-x-support#dis-post-446441
<![CDATA[MODx Parse Error due to single quote]]> https://forums.modx.com/thread/80902/modx-parse-error-due-to-single-quote#dis-post-445901
If in the text there is a single quote ' everything is fine. However, if a single quote iss inside other quotes (e.g. "'" or `'`) a parse error on the page appears due to a mistake in SQL syntax... So, in this case single quotes are not escaped in the DB.

Any ideas?]]>
https://forums.modx.com/thread/80902/modx-parse-error-due-to-single-quote#dis-post-445901 Thu, 06 Dec 2012 03:34:20 +0000 https://forums.modx.com/thread/80902/modx-parse-error-due-to-single-quote#dis-post-445901
<![CDATA[Upgrade to 1.0.7 error on line 36 protect.inc.php]]> https://forums.modx.com/thread/80822/upgrade-to-1-0-7-error-on-line-36-protect-inc-php#dis-post-445301
Parse error: syntax error, unexpected '&', expecting T_VARIABLE or '$' in /usr/home/noekde/www/htdocs/manager/includes/protect.inc.php on line 36

I don t know what the problem is, I resolved it by editting line 36, I got rid of the ampersand, but is that safe?

 foreach ($target as $key => & $value) {
to
 foreach ($target as $key =>  $value) {
]]>
https://forums.modx.com/thread/80822/upgrade-to-1-0-7-error-on-line-36-protect-inc-php#dis-post-445301 Sat, 01 Dec 2012 05:21:01 +0000 https://forums.modx.com/thread/80822/upgrade-to-1-0-7-error-on-line-36-protect-inc-php#dis-post-445301