Forum Replies Created
-
Posts
-
Hey Ismael,
1) No I didn’t. I explicitly wrote that I used php code in the page itself as plain text
2) The doc is useless, the product slider is neither enlisted nor described. Actually I used the ALB to configure the slider itself then switched to the classic editor and so got my shortcode parameters
No, no issue at all but the following points:
a/ the online doc is not complete, many shortcodes are missing and the ones described usually show only a few parameters
b/ it is currently not any more possible to write php code using the classic editor, therefore not possible to evaluate anything before a display (while with Abundance it is!)
c/ it is only possible to uses plugins which create shortcode with user defined php functions BUT Enfold do not accept cascading calls to shortcode!
Yes Ismael, you’re right, everything’s fine and Christmas is almost there.
Best regards.
Gilles
By the way, I was said a year and half ago that Abundance wouldn’t be let down. Keep waiting and see nothing but I’m still believing Santa Claus would come for me.Hi,
Since nobody seems to be willing to help, I went deep into the code, found why the entry-title content truncation worked randomly and fixed it.
If anybody is interested in here are the issue and the fix:
in functions-enfold.php:if(!function_exists('avia_post_nav')) { function avia_post_nav($same_category = false, $taxonomy = 'category') { ... $the_title = isset($entry->av_custom_title) ? $entry->av_custom_title : avia_backend_truncate(get_the_title($entry->ID),75," "); ... //Ismael's fix $the_title = strip_tags($the_title);The problem is that, while carefully coded, avia_backend_truncate() deals badly with span and spaces if present in product title. The 75 characters length and the double space break are not respected. As a result the truncation seems working randomly.
To get a strict 75 characters maximum chain length, it should be fixed as followed:$the_title = isset($entry->av_custom_title) ? $entry->av_custom_title : get_the_title($entry->ID); ... $the_title = avia_backend_truncate(strip_tags($the_title),75," ");Consider the thread as closed.
Best regards.
GillesHi,
Thanks for you kind answer.
Ismael’s customization only avoids layout breaks. it doesn’t fix or explain the disturbing entry-title content truncation.
I’ll be waiting for any further answer.
Best regards.
GillesHi,
Why? Don’t have any answer to provide to the following questions?
1/ how to improve the fix? I mean at least augmenting the number of characters and lines displayed?
2/ how to filter and maintain it in enfold-child/functions.php instead of loosing the fix each time Enfold is updated?
3/ what about the content (entry-title) which is never entirely displayed (truncated or ellipsis truncated) even if the avia-post-nav prev and next have their dimensions up sized or if the font used has its size reduced? (from my own point of view the code is buggy here since it breaks the content randomly)
Thanks for any kind help.
Best regards.
GillesHi,
Forget it.
Anyway, would you be kind enough to help me answering the questions I asked in my previous message?
Thanks in advance.
Regards.
GillesHi,
Thanks for the tip which appears to be a harsh solution.
You see, entry-title is a semantic chain which has to be displayed in a specific order: illustrator (if exists), author, and title, this one has to be display after a line break. Displayed now it fits quite the container. Well, thanks. As a result it emptied the semantics expected. That’s why it appears to be a poor solution mostly because regardless to the semantics, entry-title is randomly truncated (between 39 and 58 characters, and 2 to 3 lines displayed)
Nevertheless, several questions remain regarding the avia_post_nav:
1/ how to improve the fix? I mean at least augmenting the number of characters and lines displayed?
1/ how to filter and maintain it in enfold-child/functions.php?
2/ what about the content (entry-title) which is never entirely displayed (truncated or ellipsis truncated) even if the avia-post-nav prev and next have their dimensions up sized or if the font used has its size reduced?
3/ what about the avia-post-nav prev and next background color & opacity which seems not to be modified (please read my previous message) ?
Styling avia-post-nav is not that simple!
Thanks for any kind help
Kind regards.
GillesHi Mike,
Thanks for your answer.
Your tip doesn’t work. Sorry, already tried it.
By the way the tip given in https://kriesi.at/support/topic/styling-the-previous-and-next-arrows/#post-368727 :/* Background Color & Opacity */ #top .avia-post-nav:hover{ background: rgba(0,120,215,0.5); }doesn’t work either even whend forced with
! important
I guess I’ve tried everything I know.
Any help would be much appreciated.
Best regards.
GillesHi Rikard,
You’re right.
That’s why rather a bouble checking process would be needed or the button should be shown only if asked to.
You see once any page layout has completeley broken down, moreover, if it messed up the ALE, usually because of direct php or html code in ALE elements, it’s hard or quite impossible to go backward.
Anyway thanks for considering the idea.
Best regards.
GillesHi Rikard
Problem solved.
Anyway, an “erase evertything” or “reset to blank” button might prove to be usefull when the ALE messes up.
Best regards.
Gilles
