Driving myself insane trying to figure this out..

Hey everyone,

I’ve got three issues.. sorry if this post comes off as a little hostile but I’m extremely frustrated at the moment.

1) I’m a little confused as to why this happened so maybe someone can enlighten me. The css around the main content on one of my pages was not like the others. After an hour of trying to figure out why the f it wouldn’t let me change the css, I unchecked the box to toggle viewing of actual code for tinyMCE, and it had a whole bunch of garbage css around my [[!getResourceTag......]]. I removed it.. and viola, fixed. Any idea why this would happen?

2) I’m using the following in a chunk to show the beginnings of the resources content.

[[+introtext:default=`[[+content:ellipsis=`600`]]`:cdata]]

I’m under the impression this would print the introtext if the resource has it.. and the first 600 characters of the resource otherwise.

However.. what appears to happen is that in Chrome, it always shows the first 600 characters. In Firefox, it only shows the introtext. If there is no introtext then nothing is shown.

3) WHY?! does my modx randomly get stuck in this infinite loop of saving a document. I’m forced to refresh the page and remake any changes I made since the last save, and it happens a good 20% of the time I try to save. Maybe this is just a Chrome specific issue? Either way it’s driving me insane!

Thanks for your help!

1. I suspect that you pasted the code from somewhere and that CSS came along for the ride. TinyMCE will sometimes add annoying tags, but usually not CSS.

2. When multiple output modifiers are parsed by a snippet like getResourceTag, they often don’t do what you want them to. I can’t see how which browser you use could affect this, though, since all the processing would occur before the output goes to the browser.

3. It doesn’t sound like MODx (or Chrome, for that matter). Are you on a shared server? If so, the DB server may just be overtaxed.

Thanks for the response

1) I believe this was the case, as I wouldn’t have noticed it since TinyMCE hid it right away. The css code was so obscure I have no idea where it came from.. but.. whatever.

2) I don’t understand why this would happen either.. however I’ve had a friend look at it from his computer and say the same thing.

3) I contacted my provider (HostGator) and they said the load on the server was very low with the DB server receiving very few calls. I guess I could try editing in Firefox and see if it continues. I’ll go to save, and then it just keeps filling up to 100% over and over again. Eventually it finishes saving, but it can go on like this for around a minute before it does so.

Are any plugins attached to the events involved in saving a resource (e.g., OnDocFormSave or OnBeforeDocFormSave)?

Is the automatic_alias system setting turned on?

Only plugins I have are QuipResourceCleaner and TinyMCE

Packages I have installed - getpage, getresources, quip, taglister, tinymce
All packages are up to date and I’m running the most recent version of modx (though this saving problem happened in the previous version too)

The automatic alias setting is on.. I use friendly URLs.

I don’t currently have DB caching on.. donno why that’s relevant but I noticed it and wasn’t sure if it should be off =p

Thanks again

I would suspect TinyMCE if it only happens with resources where richtext is selected.

Is there anything in the MODx error log?

Do those errors coincide with the times it happens? I would clear the error log and look at it the next time you have trouble.

Check your snippet tags on the offending pages for any malformation. Feel free to paste the snippet tags in here.

Do you have MODx 2.0.8? It fixes a bug with the cache that could be related.