Welcome, Guest. Please login or register.
Did you miss your activation email?
14 May 2008, 12:06

Login with username, password and session length
Home Chat Help Search Calendar Login Register
Pages: 1 [2]
Print
Author Topic: EXPAND SECTION XML ERROR  (Read 1193 times)
0 Members and 1 Guest are viewing this topic.
hans30
Forum Member
*

Karma: 0
Offline Offline

Posts: 11


« Reply #15 on: 05 Mar 2008, 07:33 »

Thanx,

but I dont see solution

My version CMS --- 1.2.3.

PHP INFO
Logged
JeremyBASS
Forum Member
*

Karma: 0
Offline Offline

Posts: 114

Location: Lewiston-Idaho


« Reply #16 on: 05 Mar 2008, 14:20 »

so a full install was the only way? or will just the core work?
Logged
hans30
Forum Member
*

Karma: 0
Offline Offline

Posts: 11


« Reply #17 on: 10 Mar 2008, 04:54 »

I didnt try to reinstall core modules.

Logged
JeremyBASS
Forum Member
*

Karma: 0
Offline Offline

Posts: 114

Location: Lewiston-Idaho


« Reply #18 on: 10 Mar 2008, 10:41 »

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? 
Logged
spod_dmd
Forum Member
*

Karma: 0
Offline Offline

Posts: 9


« Reply #19 on: 26 Mar 2008, 19:19 »

I had a similar problem on previous versions of CMSMS (see my old and sadly neglected post: http://forum.cmsmadesimple.org/index.php/topic,16334.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.
Logged
Pierre M.
Support Team member
Support Guru
Power Poster
****

Karma: 28
Online Online

Posts: 2389

Location: Paris

Please keep it simple


« Reply #20 on: 27 Mar 2008, 11:22 »

Hello,

thank you for providing informations.

I had a similar problem on previous versions of CMSMS (see my old and sadly neglected post: http://forum.cmsmadesimple.org/index.php/topic,16334.0.html) and have the same issue on sites upgraded to 1.2.3

This is confusing me :
-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.
Logged

-- Pierre, support team member. comodérateur du forum francophone.
Please read "how to submit installation/debug help requests" before posting. Don't send private messages to ask for support.
Want to contribute to CMSms ? Improve the wiki with your forum account.
spod_dmd
Forum Member
*

Karma: 0
Offline Offline

Posts: 9


« Reply #21 on: 30 Mar 2008, 22:33 »

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.
Logged
spod_dmd
Forum Member
*

Karma: 0
Offline Offline

Posts: 9


« Reply #22 on: 30 Mar 2008, 23:01 »

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.
Logged
xnau
Forum Member
*

Karma: 0
Offline Offline

Posts: 21


« Reply #23 on: 23 Apr 2008, 14:20 »

I can confirm that uninstalling the True Type Text module fixes this issue.
Logged
JeremyBASS
Forum Member
*

Karma: 0
Offline Offline

Posts: 114

Location: Lewiston-Idaho


« Reply #24 on: 23 Apr 2008, 14:52 »

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...
Logged
blast2007
Forum Member
*

Karma: 1
Offline Offline

Posts: 168

Location: Italy



« Reply #25 on: 23 Apr 2008, 15:14 »

Try also this!

Regards
blast

Logged
Pages: 1 [2]
Print
Jump to: