Archive layouts (only) not loading in Cornerstone

[KEXINO]

HI all,

Since updating to Pro 6.5.5 I’m having an issue with getting Cornerstone to launch archived layouts - either existing ones, or when trying to create a new one.

‘Pages’ load in Cornerstone without a problem. However my ‘archived layout’ (a blog index page, in my case) doesn’t load. I get the dreaded “iFrame response incomplete” message.

What’s worse is the blog index page doesn’t load on the front end, eventually timing out with a 502 server error. At the moment, that means my blog index page and 4-page pagination isn’t loading on my site at all.

I tried to create a new archived layout, but that didn’t load in Cornerstone either.

I’ve tried disabling plug-ins, deleting cache, etc. Running the latest version of WordPress. Could someone please take a look and let me know what’s up?

Thanks in advance.

[tristup]

Hi KEXINO,

We have tried to check it through the WordPress admin dashboard, but unfortunately, the given credentials are not working. Can you please check and send it again?

Thanks

[KEXINO]

Password has been reset. New pw in SN

[tristup]

Hi KEXINO,

I have checked your website and found the issue you are having with Archive Layout only. I suspect there might be some different reasons behind your issue. I would like to suggest troubleshooting the following common issue to help us to recognize the reason.

1.Theme Related Issue
2.Plugin Conflict
3.Theme Update related issue
4.Child Theme Related issue
5.CSS/JS Customization
6.Disabling Cache
7.Disabling CDN

If you discover that an issue is coming from a custom code or 3rd party plugin, kindly consult with a developer or contact the plugin author. Please note that we do not provide support for custom codes and 3rd party plugins.
If none of the above helps, please copy your live site to a staging server so we can troubleshoot freely without breaking your live site.
And give us access in the secure note, including:

– WordPress Site URL & Login URL
– WordPress Admin username/password

To create a secure note, click the key icon underneath any of your posts.

Thanks

[KEXINO]

I’ve explained that I’ve done the basic checks before contacting you guys. You confirm there’s an issue - yet leave me to create a staging server?

I remember the days when Themeco support would go above and beyond to address issues. Clearly that’s no longer the case. I have to wonder why I’m paying for what is euphemistically called “support” when I’m the one doing the heavy lifting.

I’ll try to address the issue myself, thanks.

[tristup]

Hi KEXINO,

I am sorry that the answer disappointed you. To narrow down the cause behind the issue troubleshooting is required. Apart from disabling the plugins and updating the WordPress version, there are a few points that need to be checked before we come to some conclusion and do further investigation. To avoid breaking anything on the live server, we always request that staging be created so we can freely test everything. I would request you create a staging, disable the Cloudfare on it, and share the credentials for further investigation.

Thanks

[KEXINO]

After spending a long time investigating this, it seems there’s a issue with Pro and one of the plug-ins I’m using, WPSSO.

After I approached the plug-in developer, they narrowed it down to the way to an issue with WP content filters or shortcodes. Of course, they say the fault is with Themeco badly coding the content filter and nothing with them, but then they would say that, right?

I’ve set WP to pull 75 blog posts for each index page - and there are four index pages. I’m guessing that’s pushing the db autoload too hard and giving me the 502.

• Is having 75 blog posts as the index page too many? I’ve tried reducing it to 30, and everything works. However I’d like the minimum amount of pagination possible.
• Is the Pro archived page content filter coded is less than optimal? If so, do you have a roadmap for when it will be addressed?

[ruenel]

Hello @KEXINO,

The default WordPress number of items is only 10 items. Increasing the number will be at your discretion. I am not sure how many items will be the maximum for a decent loading speed of the database.

Please be advised that for all of the archive layouts, the theme only relies on how many items you have set in the General Settings. It does not have its own set of items or settings. As for the page content filter, it is best to use the excerpts on all the archives to lessen the rendering shortcode that you have added in the post items.

Hope this helps.

[KEXINO]

Thank you, I’m aware how the WP settings effect the number of pages that are output in an archived page. That’s why I mentioned how I had experimented with changing that number to find a one that didn’t bork my server.

However, I was unaware that I had it set to “Full Text” instead of “Excerpt.” My index pages only show excerpts, so thank you for bringing that to my attention. I’ll change that now.

Maybe this will now allow me to increase the number of posts to load per page. Wish me luck!

[christian]

Glad to hear that @KEXINO.