Weird behavior after upgrading to 2.3.1

Dear Modx-people,

I upgraded my site from ModX 2.3.0 (as it was quite buggy) to ModX 2.3.1.

After I made "friendly URL's" work (following the ModX manual), I changed the basic .html --> .php in "content types", so my url would end on ".php"

Weirdly, suddenly all snippets, resourcesCalls etc with a "!" in it, just start showing up as regular text on the site [[(getImagelist ... ]], even the Wayfinder.
After I deleted the "!", they magically reappear ...

But (I noticed another post for 2.3.1 with this problem) I can't call "snippets" properly as before. I cannot even implement an Iframe.

I am strongly considering to downgrade to the good old version 2.2, is that possible ?

Do you experts have some tips or reasons why my whole ModX site suddenle starts acting weirdly ?

Thanks a lot

Why do you need a .php extension? Have you tried changing it back to see if that resolves the problem?

Hi Dan,

Thanks for asking, indeed I needed php - extensions as there were quite a few links in google indexed that I wanted to get to those proper .php-pages;

As a matter a fact, I reversed all the settings to .html -extensions, I disabled friendly URL's, I put everything back as before. Modx just seems to have "snapped" ever since, and didn't recover. All chunks, getresources, getimagelist, that I perfectly used before with a "!" in "[[!" now just were printed as text ...

The problem with using chunks and Iframes (google places) has befallen another Modx-soul, after upgrading from good old 2.14 to 2.31
https://forums.modx.com/thread/92576/can-t-edit-input-any-widget-iframe-code-in-modx-revo-2-3-1-templates-chunks#dis-post-505820

Who has the knowledge to help me with this problem, please ?

greetz

The ! stops MODX using a cached result. So basically, your installation is failing to execute the php in the snippets, but will deliver a cached result from before it broke. My guess would be changing the file extensions to .php borked something in the backend.

I still don't understand why you need a .php extension. If you're worried about losing pages already indexed by Google on an old site, set up a 301 redirect in the htaccess and Google will update the links in it's index.

What if you manually delete the cache folder? Check the error logs for hints to what is going on!

Quote from: mrhaw at Aug 07, 2014, 02:59 PM

What if you manually delete the cache folder? Check the error logs for hints to what is going on!

Hi mrhaw, I deleted the contents of the cache folder, but the same result. everything I call with [[! just gets printed as "text with [[!"



Quote from: absent42 at Aug 07, 2014, 02:49 PM

The ! stops MODX using a cached result. So basically, your installation is failing to execute the php in the snippets, but will deliver a cached result from before it broke. My guess would be changing the file extensions to .php borked something in the backend.

Dear Dan, thanks for the explanation. After I deleted cache folder, the same issue remains ...

I am a bit confused, as a ModX-idiot ... :s

What about my second suggestion?

Do you have the manager_theme System Setting set to: default? If not, try that.

Quote from: BobRay at Aug 10, 2014, 06:02 PM

Do you have the manager_theme System Setting set to: default? If not, try that.

Dear Bob, thanks for the tip. I checked it, and it seems to be "default".

What is strange, is that all settings have a label "last edited Jan 01, 1970 01:00 AM



Quote from: mrhaw at Aug 09, 2014, 08:55 AM

What about my second suggestion?

Hi Mrhaw, thanks to you, I learned something new. There were indeed a lot of error reports regarding "phpthumbof" ... But that was probably during the "trial and error" constructing of an image gallery.

That date is the default date if there is no timestamp or there is a bad timestamp. That is the beginning of the "UNIX" era, and timestamps are counted in seconds from that date.