[BECAUSE it is invalid HTML, use escaped character] Import accepts > and = but not <

More
9 years 2 months ago - 9 years 2 months ago #56352 by woluweb
Hi,

I use the Import function a lot.
In one the of the fields I imported, the input was like "short film (< 30 min)", "long film (>= 60 min)" etc.
For some reason I ignore and I don't understand, I discovered that the characters > and = were doing fine... but that the character < would cause a problem :
the < itself and all the rest of the string would simply be scrapped.

(I noticed this while importing, but I think it is the same if you edit the value of a field manually)

My need was urgent, so I found a workaround (using &amp;#60; in my csv file, instead of <).
But I thought it could be useful to share this...

Txs,

Marc
Last edit: 9 years 2 months ago by ggppdk.

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

More
9 years 2 months ago #56386 by ggppdk
Hello

that is done by the save operation that is removing invalid HTML

please remember that the description accepts HTML and:
< 30

is invalid HTML
valid HTML is:

&amp;#60; 30


-- 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...
The following user(s) said Thank You: woluweb

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

More
9 years 2 months ago #56388 by ggppdk
Hello

also there is no simple / safe way for the import task to identify what is "HTML" and what is mean ... not to be HTML !


-- 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 2 months ago - 9 years 2 months ago #56401 by woluweb
Thanks Georgios,

So, this was not a bug, but a feature ;-)
Anyway, I had found the workaround/solution with the & #60; or & lt;
But I was puzzled since > was accepted and not < ...

Txs for the reply & see you soon,

Marc
Last edit: 9 years 2 months ago by woluweb.

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

Moderators: vistamediajoomlacornerggppdk
Time to create page: 0.498 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