Goodbyte wrote:
I've modified the PostProcessing-method of interpreter.fireboard.inc.php a little bit. This change should result in better performance because there's only a quite simple regex tested for the whole post.


I would like to try your modification, but i didn´t understand exactly what I should replace in interpreter.fireboard.inc.php?
Would it be possible to get whole modified interpreter.fireboard.inc.php text?

Sorry, but I´m a beginner with PHP

@KingBT: You don't have to shout...
If it has to do with large posts the it occures quite sure because of some regular expressions (there was an issue with some encoding-related regex). In this case I'd guess that your computer has more ressources available (RAM, CPU-power, possibly script-time) than an (shared?) webserver.
Try to set your WAMPP-machine under heavy load with some hard benchmark or burn-in-test and try it again.

@Admata: Quite at the beginning of the file is the PostProcess-function. Just replace the whole function by the one from my file.
I have local modifications in my local interpreter.fireboard.inc.php

@KingBT: If there is really "..." in the link, could you please try to disable trimming of long URLs in the backend?

UPDATE: I have been chasing a SEO bug the past two days. It's causing the sh404SEF cache to overflow (grow way too big) within days starting to impact performance.

Finally found the root cause: The post links in the RSS feed module and in PDF are still old style and not de-duped like the rest of default and default_ex.

Will attend to that right now...

Goodbyte wrote:
@Admata: Quite at the beginning of the file is the PostProcess-function. Just replace the whole function by the one from my file.


Got it. I must have been blind earlier. Working otherwise fine, but still sometimes breaking words before ö or ä letter. Mysterious thing.

Fb1.0.5,j1.5.5

Issue with color tag,

to make it work, at least as far as I know, you select text, open dropdown and select color.

Now, first time, you do, it says colourtandart, and if you select some, and change it to other color, works

But if you wanna reaply the same color, on another selected text of the post, it does not work

you have to pick another color and then you can reaply first one used

Not a big problem, but a nuisance to have to go deleting code or copy&pasting it

Goodbyte wrote:
@KingBT: If there is really "..." in the link, could you please try to disable trimming of long URLs in the backend?

Trimming & gzip compression dezactivated, but same result blank page and post is corupted

@Admata: This patch doesn't address the additional spaces. It just speeds up the postprocessing (auto-embedding and trimming).

@kingBT: Could you please post the corrupted link (the original one without any modifications. If you want to masquerade your host then replace character by character so the charactercount stays the same.)

@kingBT: Could you please post the corrupted link (the original one without any modifications. If you want to masquerade your host then replace character by character so the charactercount stays the same.)

Not the url is corrupted, the post is corrupted (its blank, only those with aproximativ 9000 chars)

The forward url is www.site.net/forum.html?func=view&am...155&id=34#34 and the page is blank.
In the Recent Discussions and Categories the url is http://www.site.net/forum.html?func=view...;catid=155&id=34
But this is the same as on WAMP Localhost where everything works fine.

About the encoding its ANSI and I overloaded my computer and still the posts on localhost don`t get "corrupted".
I don`t think that it something to do with the server (it`s not a dedicated one) because everything works fine.

I`ve done a 9000 chars testin on BoJ and seem to work. I`ll try to figure out whats wrong with my configuration.

EDIT

I looked in the database and the post with 9000 chars is there, dont know what to say.

Ok... I think I can't help you any more. My last (quite desperate) suggestion would be to check this encoding-regex and possibly my patch some posts ago in this thread. But to be honest, I don't think this solves your problem...