Swear filter x 2 Framework, plus XOOPS own = just lost article posting after all work lately to speed things up again..... like oh no i give up....yet that’s not like me....so further investigation led me around in XOOPS circles..... checking my own work on article to find out if a mistake.....checked everything and then last tried some latest things been playing with....... mainly the swear filter and changing it for censored......... yet thought would check it, as it had led there..... sort…A..... in terms of small submission were ok, yet not large forms in Article and now realize also CBB....
Now to begin article would not post correctly, on both live site and home one, which on 64bit AMD 3400Mhz, with just me on it, it should handle a submission in seconds, yet haven’t tried long posts for awhile, as been playing so much with web dev.....


anyways point being in hopes of maybe, switched off word censor, and wow worked in seconds, not crashing server as to much time to process, article has now speeded up loads and has the overall whole site....

So seems we have a hang up in the system, just thought should tell everyone as some people maybe wondering like me was why their sites are going slower and then panic........... clean the whole of Xoops....... change all your html to tpl.......... modify your whole MySql system........etc......... just to find it was the textsanitizer and a long censor word list.....Oops!
Worst is it sounds like my name and stuff like this always happens like that Zanitizer….......if only I had kept it simple

by wizanda on 2007/4/16 19:00:35
____________________

Thanks for an interesting post... (update)
I always enjoy your posts even when I am not having that problem at the time.

BS

Whenever regexp is involved, your site will slow down significantly.

That's the reason for a "compilation" being considered seriously in new CBB release.

hmmm Never thought about that.
Did you have a long censor list?
We have one but...its not all that big of a list.


In other words do you think simply enabling it has an effect? Or do you think it was the length of the censor list?\

-thanks for sharing

Interesting thoughts Wiz .. you do have some good ideas

Mine was correlated from open source wiki's and many sources thinking it was something we all needed (it is still in my Zoops download files), in a way some of the entries weren't needed, yet even after removing any suspect ones like fuel-source, fuelling-cheapest etc still wouldn’t allow submissions = (time of MySql expired on long posts) Which to begin worried me as having done lots of changes and thought it might have been by me…..

Yet for ages now, XOOPS hasn’t been what I joined and has begun to take longer and longer to post or just fail as many people mention and then leave.

It is the frameworks one that is causing the problem and why told DJ straight away....

As now submission work and even with a limited number of entries in censor words, still saw a massive delay in everything concerning the sanitizer to extent of failing MySql due to time.
Basically it looks it has to reference each censor word, against each post word.
May try in a bit if it is being done twice, as to say that it is the framework alone is wrong…as that is the exact same code of the normal module sanitizer, only difference could be if it is doing more work or doing it twice some how…which have yet to figure out if it is doing…..

I can't follow you all the way here Wizanda.
Are you saying that Frameworks (phppp) causes the trouble or the framework of the sanitiser?

hmm yes, now Im confused.
What was it wizanda?

-thanks!

This is to say that the censor words of the framework text-Sanitizer, is where I noticed the problem to begin, on submissions to any bit using it, there is massive drag.
The systems not using it, it is much quicker....so possibly it maybe running twice or the extras added are causing a delay.... yet on switching off the Censor words alone in admin has increased my overall site speed loads and fixed the drag....so guess then it wouldn't be the extras and so possibly something is wrong, if you can make large submissions with the normal, yet the framework takes to long for MySql on large submissions.
Yet unsure at present where the difference comes from, as submission to either is the same code….