Hi @cdelagarza,
Please see the link in the secure note, you can download the beta version of the theme.
Thank you.
1 Like
Thanks for the download.
I have now used the version in staging and took as a test an existing layout that we had copied […] (1) (1).
As you can see: I just renamed the layout and after opening the post the layout broke or was not assigned anymore. So, unfortunately, the beta does not fix the problem.
Here is still the problem that the layout assignment does no longer match.
You can check that in the staging environment. Please let me know if the login works for you.
Hey @cdelagarza,
I still see the issue on your site but it doesn’t happen on my site so there is something on your server that corrupts the layout when it’s renamed.
I’ll get some input from our development team as to why just renaming a layout in your site corrupts it and assigning it to a post no longer works.
In the meantime, would you mind setting up a fresh test site in a completely different web host and test Pro there. This is just to add up to the theory if this is a server issue.
Please also give us FTP or server access to your staging site.
Thanks.
1 Like
Now we are at a good starting point. Thanks for sharing the videos, it helps to visualize the problem better. It’s really a weird bug from my point of view, also hard to describe. But I think now you know exactly what I mean.
At the second video, what does priority -1 under assignment mean?
I’ll get some input from our development team as to why just renaming a layout in your site corrupts it and assigning it to a post no longer works.
That would be awesome, thanks.
Hi @cdelagarza,
The Priority comes into play if you have two assets that might potentially overlap in some instances, allowing you to specify which should take precedent over the other. In these cases, the layout with the lowest priority will be used.
Hope that explains about -1 priority.
Thank you.
Could it be that the cache plugin is causing the problem? WP Fastest Cache.
Hey @cdelagarza,
I tested clearing the cache and deactivating all 3rd party plugins but the issue persisted so what I think now is it’s something in the server setting that is causing the issue.
Please stay tuned and thanks for setting up the FTP access. It would be best to set up a password for us though as we might miss the email in info@theme.co as it’s also used in other messaging as well.
Thanks.
1 Like
Please stay tuned and thanks for setting up the FTP access. It would be best to set up a password for us though as we might miss the email in info@theme.co as it’s also used in other messaging as well.
Please let me know if this is working for you, if not I can create that new account with one of my emails and setting up an individual password.
Hi @cdelagarza,
It would be best if you could create an account for us then just add all the details in the secure note.
Thank you.
New SFTP access
Hi Christian, do you have an update yet?
Hey @cdelagarza,
Your suspicion is right. It is the number of layouts that affected the assignment. As to why though, we are currently investigating.
So for now, this has no solution but to rethink how you’ll going to approach showing unique content per post.
One way to achieve that is to use a combination of a Custom Single Post layout using the Layout Builder and Dynamic Content.
Thank you for understanding.
Do you have any idea or plan how to fix this?
There is a lot of content and bringing it all into other formats would mean a disproportionate amount of work just because there is a max cap?
Hey @cdelagarza,
Regretfully, we have no idea yet as to what can improve this.
Also, there is no max cap per se but rather a limitation by the server. As an example, other servers could power thousands of WordPress posts but a shared host could handle a hundres.
Anyway, it’s really not recommended to have a specific layout per post. I understand it would take you some time and work to scratch your current setup and use the Layout Builder but there is nothing we could do for now.
Thank you for understanding.
So this is a problem of the hosting / provider? What can I say or ask them to override the limit?
Don’t get me wrong, the client just booked a pretty decent server package which should have quite enough power to handle this.
I don’t really get this, sorry. What do you recommend instead?
I don’t know any other way to display blog content with x/pro.
What other way could be viable? Using a single layout but different global blocks?
Hello there, not from themeco but was interested in your subject.
Layout is used mostly for content that will repeat over and over.
If all of your posts are different, you could just build one with PRO.
Under PRO Settings, you need to check “articles or Posts” in order to see the “edit with PRO” when building a new Post. Then you just need to build it with pro. If it is a matter of speed, you can just build it once, save the whole post as a preset, and then apply a preset everytime you have one more article/post to publish.
I don’t know if this is clear, but i’m running multiple websites that are displaying a lot of article/posts and everything run smoothly, so you should be fine ! 
1 Like
Hey @cdelagarza,
Right now we couldn’t say it as we haven’t found the exact cause of this issue. Maybe there’s something we need to improve.
Yes, use the Layout Builder >> Single Layout. Not Global Blocks though. I’d recommend the use of ACF Pro to hold post specific content. You can learn more about ACF Pro and how to output data in the builder in the videos below:
- Loopers: Getting Started with ACF Pro
- Loopers: Setting up an ACF Pro Gallery
- Loopers: Nesting Repeaters with ACF Pro
Hope that helps.
This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.