[quote="hans30"]
Thanx,
but I dont see solution
My version CMS --- 1.2.3.
PHP INFO
EXPAND SECTION XML ERROR
-
JeremyBASS
Re: EXPAND SECTION XML ERROR
so a full install was the only way? or will just the core work?
Re: EXPAND SECTION XML ERROR
I didnt try to reinstall core modules.
-
JeremyBASS
Re: EXPAND SECTION XML ERROR
so you just started from scratch? I really don't like that idea... would anybody know what the safest way to fix this besides a full reinstall?
Re: EXPAND SECTION XML ERROR
I had a similar problem on previous versions of CMSMS (see my old and sadly neglected post: http://forum.cmsmadesimple.org/index.ph ... 334.0.html) and have the same issue on sites upgraded to 1.2.3
No real solution so far, a clean install of 12 live client sites is just not an option as a solution I'm affraid.
I have 2 early sites that haven't yet been upgraded running 1.0.6 that don't have this problem and 1 later running 1.2 that is also mysteriosly fine. Another 3 sites running 1.2 have the problem and all recent upgrades to 1.2.3 have the problem also.
I can't see what is different or what the common denominator is between the sites that do and those that don't.
Here is an attempt to answer Calguys questions as refers to one paticular site running 1.2.3 that has the problem:
Is this a new install? no it's an upgrade from a working 1.2
Did this work before? yes
What version of CMSms? 1.2.3
Have you installed any new modules? it has several modules installed and running but all were installed before it was upgraded and while it still worked
Have you made any changes to CMSms? no
Have you verified you meet all the requirements of CMSms? not sure what you're getting at but it was installed as normal and upgraded as normal. I use Cute FTP Pro 3 to FTP files to the server which is running a LAMP configuration and PHP5 and MySQL 5. If you need phpinfo let me know and I'll email the link privately.
I hope this will help sort out a VERY annoying bug.
Cheers.
No real solution so far, a clean install of 12 live client sites is just not an option as a solution I'm affraid.
I have 2 early sites that haven't yet been upgraded running 1.0.6 that don't have this problem and 1 later running 1.2 that is also mysteriosly fine. Another 3 sites running 1.2 have the problem and all recent upgrades to 1.2.3 have the problem also.
I can't see what is different or what the common denominator is between the sites that do and those that don't.
Here is an attempt to answer Calguys questions as refers to one paticular site running 1.2.3 that has the problem:
Is this a new install? no it's an upgrade from a working 1.2
Did this work before? yes
What version of CMSms? 1.2.3
Have you installed any new modules? it has several modules installed and running but all were installed before it was upgraded and while it still worked
Have you made any changes to CMSms? no
Have you verified you meet all the requirements of CMSms? not sure what you're getting at but it was installed as normal and upgraded as normal. I use Cute FTP Pro 3 to FTP files to the server which is running a LAMP configuration and PHP5 and MySQL 5. If you need phpinfo let me know and I'll email the link privately.
I hope this will help sort out a VERY annoying bug.
Cheers.
-
Pierre M.
Re: EXPAND SECTION XML ERROR
Hello,
thank you for providing informations.
-hans30's initial post is about using bad characters in page aliases. Once only alphanumeric characters are used, there seems to be no more "expand" error message, with plain 1.2.3.
-You link to a post with an ajax issue (a "not well-formed" error message) on 1.1.4.1.
I'm not sure you had a "similar problem" nor "the same issue".
Please explain which modules are installed and tell us if all your page aliases are alphanumeric only.
Pierre M.
thank you for providing informations.
This is confusing me :spod_dmd wrote: I had a similar problem on previous versions of CMSMS (see my old and sadly neglected post: http://forum.cmsmadesimple.org/index.ph ... 334.0.html) and have the same issue on sites upgraded to 1.2.3
-hans30's initial post is about using bad characters in page aliases. Once only alphanumeric characters are used, there seems to be no more "expand" error message, with plain 1.2.3.
-You link to a post with an ajax issue (a "not well-formed" error message) on 1.1.4.1.
I'm not sure you had a "similar problem" nor "the same issue".
Please explain which modules are installed and tell us if all your page aliases are alphanumeric only.
Pierre M.
Re: EXPAND SECTION XML ERROR
Hi Pierre
I believe hans30's original post is just about the expand all sections throwing up an XML error and not working, it was jeremybass a little later that suggested the problem was page aliases. This doesn't seem to be anything to do with the problem as all page aliases are alpha numeric except for the allowed "-" and "_" that calguy suggested are OK and are added in by default instead of spaces between words (if the page alias field is left blank when adding new content).
The problems as I said were "similar" in that both mine and hans30's problems seem to be XML related and both stop the expand/colapse all sections functions from working. (OK I said AJAX in the title of the post that I referred to but the error that I quoted from the Firefox error console says "xml not well-formed" so it's probably more to do with XML than AJAX, my mistake)
The modules installed were the same before and after upgrading to 1.2.3 Before the expand all sections worked, after it didn't.
The installed modules (listed in "extensions >> modules") are:
CMSMailer 1.73.12
FCKeditorX 1.0.5
FormBuilder 0.3
MenuManager 1.3
ModuleManager 1.1.4
News 2.6.1
NMS 1.0.5
nuSOAP 1.0.1
PageBlocks 0.1.5
ThemeManager 1.0.8
TinyMCE 2.0.5
TruetypeText 2.0.0 RC2
I hope this helps.
Cheers.
I believe hans30's original post is just about the expand all sections throwing up an XML error and not working, it was jeremybass a little later that suggested the problem was page aliases. This doesn't seem to be anything to do with the problem as all page aliases are alpha numeric except for the allowed "-" and "_" that calguy suggested are OK and are added in by default instead of spaces between words (if the page alias field is left blank when adding new content).
The problems as I said were "similar" in that both mine and hans30's problems seem to be XML related and both stop the expand/colapse all sections functions from working. (OK I said AJAX in the title of the post that I referred to but the error that I quoted from the Firefox error console says "xml not well-formed" so it's probably more to do with XML than AJAX, my mistake)
The modules installed were the same before and after upgrading to 1.2.3 Before the expand all sections worked, after it didn't.
The installed modules (listed in "extensions >> modules") are:
CMSMailer 1.73.12
FCKeditorX 1.0.5
FormBuilder 0.3
MenuManager 1.3
ModuleManager 1.1.4
News 2.6.1
NMS 1.0.5
nuSOAP 1.0.1
PageBlocks 0.1.5
ThemeManager 1.0.8
TinyMCE 2.0.5
TruetypeText 2.0.0 RC2
I hope this helps.
Cheers.
Re: EXPAND SECTION XML ERROR
Ah hah!
The culprit is the TruetypeText 2.0.0 RC2 module. It's installed on every site that has the problem (well, my XML problem I don't know if this affects hans30's problem at all).
I uninstalled then removed the module from one site and the expand/collapse all sections links miraculously started working again.
Any idea what it is about this module that would cause it to affect the workings of listcontent.php?
Any help would be appreciated.
Cheers.
The culprit is the TruetypeText 2.0.0 RC2 module. It's installed on every site that has the problem (well, my XML problem I don't know if this affects hans30's problem at all).
I uninstalled then removed the module from one site and the expand/collapse all sections links miraculously started working again.
Any idea what it is about this module that would cause it to affect the workings of listcontent.php?
Any help would be appreciated.
Cheers.
Re: EXPAND SECTION XML ERROR
I can confirm that uninstalling the True Type Text module fixes this issue.
-
JeremyBASS
Re: EXPAND SECTION XML ERROR
I can confirm that uninstalling the True Type Text module DOES NOT fixes this issue. It's just a happenstance that you have that work for you... as i did the same thing... and no change... took out all references to it... and loged out... and no change...
