Hi Ismael,

Thanks for your time with this. I have put some info in the private field with a temp login.
The translation process is still a work in progress, which is why I prefer to put the details in private. I also realise I did not phrase my question very well :-)

The real question is this:
From what I understand autop and texturize should only apply on the frontend. So the <p> tags should not be showing in the Classic Editor in Text view?
In fact that is the way it is in Text View in the Posts (non-ALB) and in the ALB editor, for example the Home Page (1 avia element at a time).
Yet on the translation window (Classic Editor) the <p> tags appear when switching to Visual view and then back to Text view.

So is this just an issue of needing to use get_the_content instead of the_content in the plugin?
And would there be any issues with Enfold if the translation editor window used get_the_content instead or some filters to make it raw?

Thanks for your help,
Rob

• This reply was modified 4 years, 2 months ago by rob2701. Reason: added note about possible performance problems hosting live site

Hi Mike,

Thanks for the good answers, very clear and helpful. I will keep you posted once the updated plugin is available.

Kind regards,
Rob

Hi Ismael,

Thanks for all the help, info and patience, I realise you guys are very busy.
All solved and can be closed. Nice!

Have a good day,
Rob

Hi Ismael,

That’s funny, I hadn’t even noticed that. I was still at the same point you were at in your last answer, that the blog archive items breadcrumb was still displaying Home / Blog / Blog / item.
All I did was create a sub menu item for the archive (blog category) with a custom link, so it would be easier for you to fix.I now see that that action has also made sure that the fix for the opened blog entries also applies to the opened blog archive entries. Now everything indeed points to the real blog page in the breadcrumbs.

I wish I could say I found the fix, but no, this was just a lucky side effect of another action :-)
Don’t know if this actually fixes the last issue you were looking to fix, or if this is a side effect issue of placing the archive page as a sub of the blog in the menu…

But there is still the minor issue left of the blog category archive page itself (so not the opened item) showing Home / Blog / Blog in the breadcrumb, where the first blog points to the real blog page. The second blog in the breadcrumb is supposed to show the item name (which in this case is “Archive for category: Blog”) but instead just says Blog.
Don’t know if that is how it’s supposed to be / intentional.

Unless you want to investigate some more, let me know – then I will keep the login to the devsite open.
If not, I’m good as it is now, thanks for all the help! Then.you can close this.

Cheers,
Rob

Added remark for ReadMore issue:
Your solution for setting the WP Settings to default cannot be used, as it results in an issue with Blog Grid pagination (404s). Blog Grid page pagination only works when the WP settings are set the same as the Homepage & Blog Settings in Enfold theme. You may want to look into that.

• This reply was modified 4 years, 4 months ago by rob2701. Reason: Added remark for ReadMore issue (pagination Blog grid 404s)

Hi Ismael,

Never mind, I managed to find a good solution in an old thread here :-)
https://kriesi.at/support/topic/remove-category-from-breadcrumb/#post-426142

// Remove Blog Category from single post breadcrumbs
// Single post shows trail Home/BlogPage/BlogCategory/ItemName
// see https://kriesi.at/support/topic/remove-category-from-breadcrumb/
// 1st element is Blog Page, 2nd element is Blog Category, remove #2
add_filter( 'avia_breadcrumbs_trail', 'mmx_remove_element_from_trail', 50, 2 );
function mmx_remove_element_from_trail( $trail, $args ) {
	if ( is_single() ) {
		unset ($trail[2]);
	}
	return $trail;
}

Topic is solved and can be closed.

Kind regards,
Rob

• This reply was modified 4 years, 4 months ago by rob2701. Reason: added code to be code

Hi Ismael,

Yes , I did indeed manage to display the Read More, but _only_ on the Blog Category Archive pages. But I don’t use those for now, they just appear — against my will :-) — because the Blog Posts when opened have a wrong breadcrumb link which points to the Blog Category archive instead of to the Blog Page (see my other post about that issue).
https://kriesi.at/support/topic/breadcrumbs-in-blog-archive-page-layout/
Because of that I have created the adapted Blog Archive page to look just like the Blog Post Elements page, so it would not be so obvious that we land on the Blog Category Archive instead of the normal Blog Page when the (wrongly set) breadcrumb link is clicked from an opened blog post. I hope I explain myself clearly this time without confusing the two.

However, I did NOT manage to get the ReadMore links to show on my real Blog Page, which is a page with a Blog Posts element. If you look at the Blog page (top menu) you will see that the link does NOT appear, even though I have set “Display Title and Excerpt + ReadMore” in the settings of the Blog Post element under “Define Blog Grid layout – Do you want to display a read more link?”. So I would like to know why it doesn’t appear there.
And yes, I have set “For each post in a feed, include” option in the Settings > Reading panel to “Summary”?, of course.
Always been that way.

I apologize for the confusion in my earlier descriptions, it was done a long time ago and I confused the two pages (Blog Category Archive and Blog Element Page) because I had made them _look_ the same because of the breadcrumbs issue.
I hope I explained it better this time… Again, sorry if I confused the issue earlier.

Thanks for your help!
Kind regards,
Rob

• This reply was modified 4 years, 4 months ago by rob2701. Reason: correction typos

Hi Mike,

Thanks for that. I added the CSS, and indeed it is different then, just more noticable :-) See for yourself.
I added a next blog post with two screenprints (png24 because more accurate), one before the CSS and one after.
To my eyes there is a definite color change for anything that has a pipe character.
In the original blogpost with the issue I added some lines with normal letters like L undercase and I undercase and b to show the difference in color better.

In short: the best way to see it is to do 3 lines in a paragraph:
xxxxxxxxxxetc.
\\\\\\\\\\\\\\\\\etc.
||||||||||||||||||etc. (pipe)
/////////////////etc.
wwwwwwwetc.
I hope I don’t need an eye doctor, or a new laptop :-)

Rob

• This reply was modified 4 years, 4 months ago by rob2701. Reason: Added best way to see it

Hi Ismael,

Thanks for looking into this. I have entered the change in the child theme functions.php (starts at line 358).

Unfortunately it doesn’t do what I wanted to achieve, probably I didn’t explain it well enough.

When I have a blog post open from the Blog page, the breadcrumb still shows:
<site>/category/blog
What I want to achieve is that the breadcrumb on an open blog post points to <site>/blog, so to the Blog PAGE, _not_ the Blog category (which is the archive page). I hope I explained it better this time.

Thank you for your help and for your patience with my explanations… :-)

Rob

Hi Ismael,

Thanks for the clarification. Almost ashamed now, I should have realised that the archive page used depends on the WP Reading setting which was indeed 12. I had only looked at the Blog Posts element itself, where I had set the number of posts to 3 and noticed no difference. Thanks for solving that by pointing it out. My bad. Works perfectly once I do the post number per page in the WP Reading setting… :-))

Added remark 2020-07-01:
Since pagination for Blog posts only obeys the “WP > Settings > Reading > Blog pages show at most:”
So what is the setting in the “Blog Posts element > Pagination > Post Number” for?
Since that is always overridden by the WP Reading setting, perhaps it is better if the setting in the Blog Posts element mentions something like “This number is taken from the WP Settings > Reading” and remove the dropdown to set the number of posts? Just a thought for the next theme update. :-)

What remains is the ReadMore button which refused to show up, even though (in the Blog Posts element) I have set it to display “Title and Except + ReadMore”. How can that be solved?

By the way, related to this are some breadcrumb issues with the archive blog page, different thread (same page on this website):
https://kriesi.at/support/topic/breadcrumbs-in-blog-archive-page-layout/

Thanks for your time! Kind regards,
Rob

• This reply was modified 4 years, 4 months ago by rob2701. Reason: Added remark regarding post number setting in blog posts element

Hi Mike,

Sorry, that was my mistake, I had deleted something from the child theme functions.php, but not well enough, left a “\\” in, resulting in the infamous “cookies are blocked” error and white screens. Fixed now.

Thanks for your continued help!
Rob

Hi Victoria,

I think I understand it now, somehow the last row in the tablet view adapted to a minimum width by not having it specifically set. Still strange that every time 1 more element added solved it too…

It’s understandable you did not see the issue before, someone would have to have tried (like I did) exactly 1 more element than the number of desktop view rows created by the chosen number of elements per row in the desktop view (whether 3, 4, 5 or 6). I mean what are the odds?
I just happened to stumble upon it by chance :-)

Thanks for your patience and help! Issue solved, you can close this one.
Rob

• This reply was modified 4 years, 5 months ago by rob2701.

Hi Victoria,

Thanks, that works well. But I also had to add some CSS to that, because as I mentioned above, the groups of 4 otherwise have too much margin between them (retained from the desktop size view) compared to the groups of 2 in the tablet size view:

/* Adjust last section/element on INFO grid row page too small on tablet */
@media only screen and (max-width: 989px) and (min-width: 768px) {
    #top.page-id-620 #av-layout-grid-1 div .av_one_fourth {
        width: 48%;
    }
  div.flex_column_div:nth-child(5),
  div.flex_column_div:nth-child(6),
  div.flex_column_div:nth-child(9),
  div.flex_column_div:nth-child(10) {
     margin-top: 30px;
  }
}

Because I always like to understand why this happened in the first place like I described above (only the very last 4n+1 element becoming a smaller size), can you explain? I fail to see how that percentage setting could affect only that last element — I did not change that with CSS anywhere, except when trying to fix the issue on tablet view :-)
see #1225329 above, this happened without any of the tried fixes from my part:
Additional info:
This ONLY happens with 5 or 9 or 13 elements, strangely enough, so at the exact points of the desktop 4-per-row+1. When you clone the last element however, so to get 6, 10, 14 elements, everything is fine again, even with the tablet size. Then the only remaining issue is the top-margin between the original desktop-4-per-row even on the tablet-2-per-row. Which can be easily fixed with CSS.
But it seems the problem is there with 4n+1 on the tablet-size view (obviously when you use one_fourth elements like me).
When using one_fifth element the same logic applies, but then for 5n+1.

I notice that in my previous fix attempt I used the wrong media query for tablet, but that has nothing to do with the issue itself.
And also, is this something that will be included in a next update?

Thanks for your help,
Rob

• This reply was modified 4 years, 5 months ago by rob2701. Reason: Added questions

Hi Victoria,

Yes of course it does, for me too, with the desktop size (4 elements per row).
The problem is with the tablet size (2 elements per row), like I wrote above. Jusr resize the browser window, you will see the issue.
Again, desktop and phone sizes are fine. Tablet size is the issue.
With the tablet size, you see the 9th element become much smaller than the others.
And when you apply the CSS (uncomment it at the bottom of Quick CSS), then you will see that size and the padding is all fixed, but then the subpages get a very narrow content space.

Kind regards,
Rob

Additional info:
This ONLY happens with 5 or 9 or 13 elements, strangely enough, so at the exact points of the desktop 4-per-row+1. When you clone the last element however, so to get 6, 10, 14 elements, everything is fine again, even with the tablet size. Then the only remaining issue is the top-margin between the original desktop-4-per-row even on the tablet-2-per-row. Which can be easily fixed with CSS.
But it seems the problem is there with 4n+1 on the tablet-size view (obviously when you use one_fourth elements like me).
When using one_fifth element the same logic applies, but then for 5n+1.

• This reply was modified 4 years, 5 months ago by rob2701. Reason: Added still more testing info of when this issue happens on tablet size view