Tagged: nextpage
-
AuthorPosts
-
October 27, 2021 at 7:06 pm #1326728
Hi,
the layout builder element “Page Split” does not work properly.
- The mouseover over the link “2” shows that a link to /permalink/2/ is planned.
- But the link ends up at first /permalink/ again.
- After switching off the WordPress URL auto-correction /permalink/2/ shows only 404 – Nothing found.
- If you add in front of the element <!–avia_template_builder_nextpage–> a block of text with a wordpress <!–nextpage–> then the page change works properly.
But I’m not really comfortable with this rustic workaround.
Best Regards,
GünterOctober 29, 2021 at 6:12 am #1326923IHi,
think there is some bug in the code. When changing from page 2 to page 1 the console shows the error
GET https://www.domain/2/ 404 not found, even though the url should be https://www.domain/page/2/(Without additional WordPress nextpage https://www.domain/page/2/ would also be empty.)
Regards,
GünterOctober 29, 2021 at 6:22 am #1326925Sorry, You need access, becaus the link is a privat post.
October 30, 2021 at 1:29 pm #1327060Hi,
Sorry for the late reply – and thank you for reporting this.
I could locate the problem and fix it for most permalink structures.
It should work for yours. Will be part of the next update.Meanwhile please replace enfold\config-templatebuilder\avia-shortcodes\page_split.php
with the content of:
Do not forget to make a backup of the original file for a fallback and clear server and browser cache.
If you need help let us know and we can do it for you.
Best regards,
GünterOctober 31, 2021 at 10:12 am #1327167Hi Günter,
unfortunately, the new page_split.php does not have the desired effect:- The page links are not displayed.
- The following page /page/2/ shows a 404 error.
- The shortcodes in the layout builder no longer work.
- The previous workarround with nextpage + avia_template_builder_nextpage no longer works either.
Before: https://www.dropbox.com/s/lql5pfvu6t5y2vs/before.jpg?dl=0
After: https://www.dropbox.com/s/vcq4jhosgf7knrl/after.jpg?dl=0
(A Portfolio page)Best regards,
GünterNovember 2, 2021 at 2:46 pm #1327472Hi,
Sorry the fix did not work.
As this element is only accessible via add_theme_support we did not get any reports up to now.
I will have to rewrite the complete logic as WP has changed some backend logic in pagination with 5.5.
I will let you know here when it is ready.
Best regards,
GünterNovember 2, 2021 at 4:58 pm #1327495Hi,
Updated version:
Can you check please.
You can remove add_theme_support and it should work without your workaround with nextpage.
Best regards,
GünterNovember 2, 2021 at 5:27 pm #1327499Hi,
the updated version doesn’t work either. But the workaround works well.
With WP-nextpage alone you can see the end tag of the container in which –nextpage– is placed on the following page [/code, text, …]
Thank you for your efforts,
Günter -
AuthorPosts
- You must be logged in to reply to this topic.