quick edit messed up after 3.0 RC2 Update ?

I did updated vbseo to 3.0 RC2 and everything works fine but when I quick edit my posts and save them again, all signs like " quoting and Ć ż ę letters are not working..

ex.

Mała dygresja. Przechwalać się jest łatwo, przedstawić jakąś mocną propozycję już trudniej...

damn.. the text gets fixed here, you have to check the attachment to get the idea.

Can you try to upgrade to vBSeo 3.0.0 Release Candidate 3 and check if the problem still occurs.

Yep, its still there after upgrade,

Additionally I get

Warning: Division by zero in /includes/functions.php on line 4497

error while posting .. :(

I had a similar problem with characters lately (not related to vbseo) Did you lately swithced servers or restore your database or upgrade your database ?

It happens whtn there is a conflict with database language collation. I advise you to check your database tables and rows and be sure that they use the same collation.

If you disable vBSEO, does the problem persist?

Originally Posted by Keith Cohen

If you disable vBSEO, does the problem persist?

Ive disabled vbseo and all problems are gone.

Warning: Division by zero in /includes/functions.php on line 4497

This is the most ennoying thing.. Every post get this message.

could switch to ioncube version sort things out ?

Hello,

do you have "Hellcats page compressor" plugin installed? We had a similar issue reported and it turned out to be related to this add-on (not vBSEO).

(And you shouldn't need a page compressor with vBSEO, since it has a built in option to optimize your HTML. )

Thanks guys, Ive removed HELLCAT's hack and this problem:

Warning: Division by zero in /includes/functions.php on line 4497

is gone

but the quick edit thing is still borken.. :(

%u0107 %u017C %u017A %u0119 %u0142

Thanks guys, Ive removed HELLCAT's hack and this problem: is gone

Great!

but the quick edit thing is still borken..

Could you please open support ticket with test account details, vbseocp password and example URL/post message that can be used to reproduce the problem?

Theres no need for this anymore it seems. The problem is gone.
I dont know how its possible, but yes it seem fixed without any action.

Thanks guys for the great support.

Ok, great!