Field value troncated before first comma

More
9 years 6 months ago - 9 years 6 months ago #53512 by renaud
Hi,

I have a strange issue with 2.2.1 rc. A field value is troncated before the first comma on frontend for a particular text field in the page. It displays "Motos O" for instance, instead of "Motos O, HST, HC4" which is the value in DB. The other fields display fine and parameters are the same for the single text fields.

Another text field, created after Flexicontent update, displays "é", "Ã", etc. instead of "é", "à", etc. Everything is in UTF-8 (.sql). I can't findout why I have this issue too.

Finaly, I have a performance issue, up to 20-30s before page loading, and can't findout why. A script conflict (jquery, etc.)?

Here is a link :
www.arbracam.org/site_content/81-plans-d...rrot/2314-11394.html
"Roue directrice avec frein HSSE, BOSS2C, NSSO, NTO" is truncated "Roue directrice avec frein HSSE" on this page, and you can see the strange characters also.

Thanks in advance for your help.
Last edit: 9 years 6 months ago by renaud.

Please Log in or Create an account to join the conversation.

More
9 years 6 months ago #53516 by ggppdk
Hello

about frontend performance we have detailed statistics
-- temporarily set parameter "performance statistics" to YES in the first TAB of FLEXIcontent component configuration
and look at the bottom of your frontend


-- Also you can check this:
PHP/DB requirements

and then
-- you can upgrade to v3 BETA5a (fancbox loading is broken, use multibox instead)
github.com/FLEXIcontent/flexicontent-cck/releases


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

More
9 years 6 months ago #53531 by renaud
Hello,

Thanks for your quick answer.

I've updated flexicontent to 3.0.0. The component looks nice. But none of the issues are fixed on my side.

Performance issue is probably due to script conflict. The issue is the same both in frontend and backend. And often a second or a third click is required to load a page which is not very confortable for users.

I still have truncated values and character issue (é, Ã,...) in two different field values on fronfend.

Please Log in or Create an account to join the conversation.

More
9 years 6 months ago - 9 years 6 months ago #53537 by ggppdk
Hello

1. for performance as i said, please enable the statistics parameter to see if it is the component,

and give specific performance numbers for specific parts of FLEXIcontent


2. about the field value truncated, if the value is saved and loaded in the item form, then reason could be other
e.g. a content or a system plugin that you have installed

so is the value saved load properly in item form ?

-- does it happen for all similar values ?
if content plugin triggering is enabled disable it


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...
Last edit: 9 years 6 months ago by ggppdk.

Please Log in or Create an account to join the conversation.

More
9 years 6 months ago - 9 years 6 months ago #53553 by renaud
Hello,

1. Statistics are enabled. I had ever checked both Flexicontent and Joomla! statistics few weeks ago. But I can't find out why I get those performance issues on frontend and backend. Perhaps there is a javascript conflict between different instances of Mootools/Jquery or other scripts. For instance, I have issues with lightbox image loading also.

2. Content plugin triggering is disabled in the field properties. The value is truncated in the HTML. The value saved load properly in item form (see the attached screenshots



). Everything is fine in the DB. The issue seems to happen randomly, just before the first comma, not necessarly with similar values. I had corrected some values with the Phpmyadmin search/replace tool. Something that works randomly, but there is nothing special in the .sql table export (no special characters for instance). Both server and browser cache were emptied also.

[strike]I still get special characters despite that all sql scripts are utf-8 encoded. A file editor bug? I replaced special characters in the DB.[/strike]
Fixed by adding "SET NAMES 'utf8';" to SQL files.

Nice new Flexicontent backend. (Will you consider using sprite images in the futur to improve performance ?)

Thanks for your help.
Attachments:
Last edit: 9 years 6 months ago by renaud.

Please Log in or Create an account to join the conversation.

More
9 years 6 months ago #53586 by ggppdk
Sprites yes that would be best, just involves some work, or some 3rd party icon-fonts


-- Flexicontent is Free but involves a big effort on our part.
Like the our support? (for a bug-free FC, despite having a long list of functions) Like the features? Like the ongoing development and future commitment to FLEXIcontent?
-- Add your voice to the FLEXIcontent JED listing with a 5-star...

Please Log in or Create an account to join the conversation.

Moderators: vistamediajoomlacornerggppdk
Time to create page: 0.767 seconds
Save
Cookies user preferences
We use cookies to ensure you to get the best experience on our website. If you decline the use of cookies, this website may not function as expected.
Accept all
Decline all
Essential
These cookies are needed to make the website work correctly. You can not disable them.
Display
Accept
Analytics
Tools used to analyze the data to measure the effectiveness of a website and to understand how it works.
Google Analytics
Accept
Decline