Michael Bourne

Appreciate the heads up. I probably should have thrown an isset() into that part to see if there was any css prior to stripping comments out.

I’ve been waiting for Themeco to announce their global blocks adaptation (which they sort of did last week). Once it;s out, I will push an update to GB explaining how to migrate everything over (and fix this notice as well for the stragglers).

Cheers

THe link for those unfamiliar:

https://xthemetips.com

Hey Edward,

Thanks for the heads up! Love the system, great way to extend Global Blocks.

Cheers

I get the same error when resending order emails from the order screen. Looks like pre orders is my culprit.

Patch above fixed it for now.

Not a bad idea, I think I can do that pretty easily. Let me look in to it.

Hey Patrick,

Great ideas! Sadly points 1 to 3 can’t be done as per Themeco rules, we are not allowed to integrate into their current UI. For point 4, what we could do it hide the text and visual editor so that the only option is to edit in CS/Pro, but launching it directly wouldn’t be possible.

Point 5 has merit, but I believe you could do it with any plugin that allows exporting of specific posts by post type. CS data is a little sensitive in the database, certain backup, migration and search and replace plugins have been known to break CS pages.

Appreciate the feedback and I hope you’re finding the plugin useful!

Sorry for the late reply, we don’t get notifications from WP about new posts. The plugin works with Pro, but after the upgrade you have to resave your permalinks. Hopefully you were able to figure that out!

There were some permalink issues with the upgrade process, generally resaving them from the WordPress settings page clears up the 404 errors.

About the shortcode, we’ve always used [global_block] since it was implemented. I’m not really certain where that other one would have come from.

Hey Michael!

This is often caused by margin or padding in either the parent container, or the block itself.

Sometimes, all you need to do is disable “column container” on the row where the global block is being places, and ensure there is no padding set in either the section, row or column.

Let me know if you can’t solve it and I’ll take a look on your site.

Cheers

Thank you for the input, Cendar. Sam, see the link he posted for a solution.

I appreciate the detailed replies! I’ll see what I can do in the future about automating it.

Hi Cendar,

I haven’t done specific testing myself, but a gentleman named Miroslav from the X users group has, and he confirmed it worked fine. He did mention there was an old way and a new way of translating, and he had to play with those before figuring it out. His final report was that is was a bug in WPML and he was able to solve it, but I didn’t hear back about the specific fix.

If you’re a member of the group, it may be worth pinging him. I’ll do the same and update you as soon as I can.

Cheers

Hi Michael,

This is an expected behaviour with Cornerstone. The recommended way to implement a one page navigation is to give each section a unique ID, then use that new ID in the nav.

When Cornerstone shortcodes get executed by WordPress, the “x-section-1” IDs are generated dynamically. Since inserting a global block adds more sections to the page, they are included in the numbering sequence. As this is a default CS behaviour, there is nothing we can do about it on our end. You might possibly get around it by giving your Global Block sections a unique ID as well.

Hope that helps!

Howdy!

Let me look into it and get back to you with a solution. I appreciate your patience!

Michael

Hey Menno,

As per our request on Facebook, send over some credentials for us to take a look. The plugin brags the content value from the database, so it shouldn’t be executing a post template. Maybe we missed something though!

Cheers