Forum Replies Created
-
Posts
-
I believe, but here it is surely buggy, I tested it quite deeply. Maybe there are some elements which add up to make 3.5 work improperly.
Create a new page
Activate page builder
Create a 1/3 column
Place a team member element inside it, use a picture, and description
Set column to have 10px padding inside everywhere
set border to 1 px, and border radius to 4pxRefresh page
Duplicate the column, and dupicate again: no refresh, css misbehaving too
go back to backend, delet a column, or two, refresh: no change
Switch off adv tinymce, go back to page refresh: at voila, everything is fine, even css
I wrote this yesterday here in the forum:
If you use advanced tinymce editor disable it, it uses ajax, and with new updates I’have found that some conflict emerges with enfold.
The temporary solution is here: Modify Enfold/framework/php/class-framework-widgets.php
Change line 1040 (in the <get posts posts> avia_get_post_list function part)
original:
echo “<strong class=’news-headline’>”.avia_backend_truncate(get_the_title(), 55,” “);to this:
echo “<strong class=’news-headline’>”.avia_backend_truncate(get_the_title(), 100,” “);Maybe we can rewrite this function in the child theme’s functions.php
On a site with a previous version of Enfold (3.2.3) it behaves as expected without error. Interestingly this previous Enfold does not shorten the title! This way it does not cause any erreneous character. Maybe you should take out this shortening code from a newer enfold.
Thank you, Mihály
Thank you, but the code you suggested would cause other problems. I requested a feature here https://kriesi.at/support/enfold-feature-requests/
OK, found, thank you.
It’s tricky to find a function if it is linked to an icon, instead of an icon with a text-label.Thank you
It wanna save the whole page as a template. But in the 3.4 update it is said to be able to save single elements not just the whole page.
Wpconfig.php is fine. Collate is set to utf8mb4. Datbase collate is set to utf8. Utf8mb4 is 100% backward compatible with utf8.
I’ve checked your theme files, seems to me that the php files involved in creating the tab part are set to utf8 (the correct one). Maybe the shortening function somewhere can cause this problem.
Unfortunately this does not help, even if I switch on Open Sans, or Arial instead of my default Georgia font.
I do not think its a problem with latin-ext subset, because the character which is in the original post is <á>, this is a standard character, not latin-extended subset, as far as I know. Maybe the php file containing the code for this tab should be set to the proper character set in its properties.
example: http://stackoverflow.com/questions/5056646/how-to-set-utf-8-encoding-for-a-php-file
Dear Rikard!
Thank you for your answer. I really appreciate your time and effort to answer me. I happen to understand this behaviour yesterday in my trial and error experiments.
I feel it’s a problem that there is no warning or any clear indication within the visual editor that the given element is a full width element. It would be good to avoid misunderstanding. I think you should arrange the visual editor top bar elements into clearly defined rows, saying that this is this or that (full widht elements, tolerates sidebar…), this is just a suggestion.
Likewise when I place a layerslider element into a page where there is a sidebar, it ruins that page because the above mentioned problems, or behaviour. Additionaly I can not place layerslider within an 1/1 element, but inside a text element using the layerslider shortcode. It should be solved somehow or documented right at place in the element as a warning or something.
Other problem: If I place an 1/3 row, and besides this 2 additional 1/3 rows, and switch on equal height, and want to use the below ‘custom top and bottom margin’ function than with this correlation it won’t take into consideration this custom margin setting. Like here, under the slider: http://oroshaza.hu/bmo/hirek/ (a test site). Now I use individual height to get the margin setting work.
Thank you. I love your theme anyway, it’s really a masterpiece in the see of wordpress themes. I hope these problems would be solved to make this theme even better.
Mihály from Hungary
Something similar issue was shown in this support forum here:
https://kriesi.at/support/topic/avia-builder-above-page-cant-use-sidebar/
