Support is really a problem

hi JFGoude
i have almost tried everything to resolve the issue but the issue is not related with our sql query.
The issue is when we are calling content plugin there content due to unknown character take utf8mb4_general_ci but in database #__content the character is utf8mb4_unicode_ci thats why we are getting error in that special character.our content is firing from onafterinitialize so the content inside article text will appeared so our sql will always give error no matter what will be the case of encoding.
i tried to find the utf value of the character as well but still unable to find that so that i can create case to replace that.
There is nothing in my hand that i can do now to fix it.the only possibility is you would talk to JCE pro and ask for solution to them else at least ask them what character set are there that are creating these smiley so i can create a case for that and remove those from searching text using PHP.

I will contact the JCE support but i am pretty sure they will tell this is not their problem (in fact if I disable SEO Glassary component, emoticon put by JCE code displays nicely)

stay in touch I will give news after contacting JCE

Ryan (JCE extension developer) responded by :

The emoji are all official unicode characters - https://en.wikipedia.org/wiki/Emoticons_(Unicode_block)

the fact is this works nicely if I disable SEO Glossary component, one way or not the problems seems to come from the SQL request your send to the mySQL database

hopefully last clues help you to find a solution

Regards

Hi,

I think Guanio is right about the database format, even if it's not 100% sure it'll solve the issue, this is something that have to be fixed before further investigation. Note that all the support requests have to be made through our support ticket, this forum is only for presale questions

Thanks !

I have fixed the issue please recheck and update on ticket support

it seems it's working now

many thanks, I have now to do the same on my main site (not the replicat),my mirror site ask to install a 2.5.4 version but I was already working with that version, so I do not download it and wait on your instructions to do the same on my production site ?

PS : just because I am a bit curious and tried a lot of things before posting here, can you explain me what was the reason that caused the bug ?

@tristan :

I know this is a pre-sale forum but I waited really a very (very, very) long time before getting a solution and even to have some news.
I think it's always better to spend 2 or 3 minutes sending a mail telling : sorry we investigate and continue to do so but have some troubles to find the real reason that's fires this bug.

I can understand there is some problems difficult to solve ( I spend all my life searching to solve problems on SQL Server databases and IIS servers)

many thanks to your team for having solved it

You need to copy /plugins/content/seoglossary/seoglossary.php to your original files.
I will update the code to 2.5.5

The major issue we are facing is that whatever I can do the code is not related to our coding at all
I already mentioned before on ticket I will check possibility for that.

Thanks,

I copied the modified seoglossary.php on production site and it worked nicely, have copied it in safe place on my sources repository to be sure not having to disturb you due to conflicts with next upgrades

Best regards

Hi,

I'm sorry but the forum is only for pre-sales questions.

Could you please continue on the ticket system.
If you have any problem with ticket system please drop us a billing ticket or a contact via the contact form.

Best regards