tags not saving in chunks in 2.0.7

Upon save, this results in "Save Successful!" (Good!):

<div class="loginForm">&nbsp;
<div class="loginMessage">[[+errors]]&nbsp;</div>&nbsp;
<div class="loginLogin">&nbsp;
<form class="loginLoginForm" action="[[~[[*id]]]]" method="post">&nbsp;
<fieldset class="loginLoginFieldset">&nbsp;
<legend class="loginLegend">[[+actionMsg]]&nbsp;</legend>&nbsp;
<label class="loginUsernameLabel">[[%login.username]]&nbsp;
</label>&nbsp;
</fieldset>&nbsp;
</form>&nbsp;
</div>&nbsp;
</div>

Upon save, this results in... nothing! (Bad!)

<div class="loginForm">&nbsp;
<div class="loginMessage">[[+errors]]&nbsp;</div>&nbsp;
<div class="loginLogin">&nbsp;
<form class="loginLoginForm" action="[[~[[*id]]]]" method="post">&nbsp;
<fieldset class="loginLoginFieldset">&nbsp;
<legend class="loginLegend">[[+actionMsg]]&nbsp;</legend>&nbsp;
<label class="loginUsernameLabel">[[%login.username]]&nbsp;
<input class="loginUsername" type="text" name="username" />&nbsp;
</label>&nbsp;
</fieldset>&nbsp;
</form>&nbsp;
</div>&nbsp;
</div>

(All the &nbsp;’s are to get around another apparent bug in the parser).

Tested in Firefox and Opera, latest versions, same result.

ModX is 2.0.7 Traditional.




Server OS: Linux, build date Jan 4 2011 , x86_64

PHP: 5.2.15

Smarty Version: 3.3.0

PHPMailer Version: 3.0.4

MagpieRSS Version: 2.0.4

Database type: MySQL 5.0.91 community

Client OS is Windows 7.

There is nothing, zip, zero, nada in the error log pertinent to these failed saves.

I have spent a whole day scouring the web, and trying to get a changelist between 2.0.7 and 2.0.8 to evaluate an upgrade.

I’m a little frustrated at the moment, and would appreciate any help.


ANY HELP MUCH APPRECIATED. I’m a PHP programmer just getting into MODx. I see its potential, but right now it’s useless to me. I’m hoping someone can help with this, and improve these initial impressions.

Thanks!

Additional follow-up:

This, "Success! Save successful!"

<div class="loginForm">&nbsp;
<div class="loginMessage">[[+errors]]&nbsp;</div>&nbsp;
<div class="loginLogin">&nbsp;
<form class="loginLoginForm" action="[[~[[*id]]]]" method="post">&nbsp;
<fieldset class="loginLoginFieldset">&nbsp;
<legend class="loginLegend">[[+actionMsg]]&nbsp;</legend>&nbsp;
<label class="loginUsernameLabel">[[%login.username]]&nbsp;
<bogustag_input class="loginUsername" type="text" name="username" />&nbsp;
</label>&nbsp;
</fieldset>&nbsp;
</form>&nbsp;
</div>&nbsp;
</div>

while this, no save successful!

<div class="loginForm">&nbsp;
<div class="loginMessage">[[+errors]]&nbsp;</div>&nbsp;
<div class="loginLogin">&nbsp;
<form class="loginLoginForm" action="[[~[[*id]]]]" method="post">&nbsp;
<fieldset class="loginLoginFieldset">&nbsp;
<legend class="loginLegend">[[+actionMsg]]&nbsp;</legend>&nbsp;
<label class="loginUsernameLabel">[[%login.username]]&nbsp;
<input_bogustag class="loginUsername" type="text" name="username" />&nbsp;
</label>&nbsp;
</fieldset>&nbsp;
</form>&nbsp;
</div>&nbsp;
</div>

There’s something with the "input" token that is throwing the parser off. This contradicts my early research which indicates that "any HTML is acceptable in a chunk."

Again, any help would be much, much appreciated!

Check to make sure you have mod_security and safe_mode turned off for PHP.

Will do. Thanks!

PHP safe mode is off in php.ini, so that’s not it.

I’m not sure that we have any control over mod_security - that’s an Apache setting if I’m not mistaken. We’re hosted by a third-party hosting service.

Has anyone else reported anything like this, Shaun? I’ve not seen anything remotely similar, and neither has my associate who is also investigating.

Also, any idea why back-to-back tags - e.g. <p>Hi mom!</p><p>How are you this morning?</b> - would also result in a non-save of a chunk? That’s what all the &nbsp;’s in the examples above circumvent - we’d love to get rid of them.

I’m suspecting our configuration is at fault.

It sure sounds like mod_security.

See this: http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me

Bob,

That’s kind of where we’re at too. We just upgraded from 2.0.7 to 2.0.8. Same problem.

BTW your guides are the most accessible, readable, and logical MODx resource that I’ve found on the web.

"A thousand thank yous" seems trite for all you have done in this area.

Hats off to you.

Thanks for the kinds words.

It’s definitely a 403 - packet tracers don’t lie. This gets MODx off the hook as the culprit for this. My apologies to Jason, Shaun and co.

I followed all of the steps at the site Bob sent, to wit, http://wiki.modxcms.com/index.php/What_is_mod_security_and_how_does_it_affect_me

Any changes to .htaccess results in "Internal Server Error" at our site, so we’re taking this up with tech support at the hosting firm.

I feel kind of like Mike Holmgren in post game comments following Superbowl XL: "When we went out there today, I didn’t realize we were going to have to play the Steelers AND the referees!"