Return message after content update Topic is solved

[smithdesign77]

I have a funny experience after updating content (url ...moduleinterface.php?mact=CMSContentManager,m1_,admin_editcontent,0&;__c=XXXX&;m1_content_id=XX&showtemplate=false) - both ways, either by "Apply" and also by "Submit" the content is INDEED saved, however instead of returning to the contens overview or receiving the little green AJAX thingy at the top all I receive is a timestamp, like

'2024-10-09 14:45:24'

So, if I click Submit this is then the only content displayed at all - and by clicking "Apply" this is the exact response what I can see in the browsers dev tools (network tab), instead of the JSON what I've just double-checked with another installation what usually should be served.

This is naggy, of course, to "Apply" and then click "back" in the browser — had anyone already experienced this or has an idea what the reason could be?
Thank you very much!

[DIGI3]

You didn't include your version or the modules you're using, but I seem to recall this being caused by CGContentUtilities. If that's the case, migrating to ECB2 is the best option.

[smithdesign77]

SORRY! ＼(_ _) And thanks for your response!
It is CMSMS Version 2.2.9.1 and indeed here are a number of CG modules still running and haven't been replaced (yet). Those are CGCalendar, CGExtensions, CGJobMgr, CGSimpleSmarty and CGSmartImage … all are somewhat updated, more or less probably (no available updates shown in the module manager).
As far I understand this the module you mentioned tho is not in my list?

[smithdesign77]

But now I get a feeling, where we are going here...
This is in the template (very first lines) - may this cause that behavior?

Code: Select all

{content block='pageheader' assign='header' label='Page header' wysiwyg=false}
{content assign='main_content'}
{content block='abovefooter' assign='abovefooter' label='Above Footer' wysiwyg=false}
{share_data scope=parent vars='main_content,header,abovefooter' scope=global}

I take this had been here for a while, most probably already with PHP5 or so…
(unfortunately I have not maintained this installation until just recently)

[DIGI3]

I may be wrong with which module was causing it, but it's most likely one of those. You could try temporarily disabling all modules not necessary for content editing and see if the problem goes away, then re-introducing a few at a time to narrow it down. If you figure out which module it is, make that your first priority to upgrade/migrate.

[smithdesign77]

Oh, oh… :[
Well, then I take we do have some work ahead. Thank you!