Section Bottom Separator Angle Out Not Working!

Hi, I’m trying to use the ‘Section Bottom Separator’ Angle Out, but nothing happens, the page loader goes red and keeps spinning around. When I save the page and then refresh, the sections background has been removed and there’s still no section bottom separator on there. I’ve deactivated the plugins to see if there’s a conflict but it still doesn’t work. I’ve included a screen grab if it helps at all. You will see that it has the ‘Angle Out’ separator but won’t change to angle in.

Thanks!

Hello @core365,

Thanks for asking. :slight_smile:

I think you may be running out of your memory. You can try increasing your PHP Memory limit. You can do this by editing your wp-config.php file which can be located under the root of your WordPress installation.

Add the following lines into that file.

define( 'WP_MEMORY_LIMIT', '512M' );
define( 'WP_MAX_MEMORY_LIMIT', '512M' );

You can add it before the line
/*That's all, stop editing! Happy Blogging. */

Check the following as well.

  • Ensure everything is up to date according to our version compatibility list here. Please follow the best practices when updating your theme and plugins. Click here for more information.
  • Go to X > Settings and click on the Clear Style Cache button.
  • Make sure that you’re running at least PHP v5.6.x or later to avoid any WordPress related incompatibility issues. If you’re not sure what your server configurations and settings are, install a plugin like WP-Serverinfo (https://wordpress.org/plugins/wp-serverinfo/) and check your server info by head over to Dashboard -> WP Serverinfo area.
  • Check your PHP Max Execution Time and set it for 300 for optimal usage.

If you still have problems kindly get back to us with the result of the steps above and URL/User/Pass of your WordPress dashboard using the Secure Note functionality of the post to follow up the case.

Thank you.

This is a bug I’ve reported last month. https://theme.co/apex/forum/t/cornerstone-buggy-in-v3/25946/7

It still remains to be fixed. Theme.co is doing a rather lousy job of keeping us informed of their progress with making the next version of their software that will fix this and other assorted issues with version 6.x.

Hi @Prasant, I did what you suggested but it hasn’t worked and it isn’t a surprise either if this has already been reported and is a known bug! It would have been more useful if I was just told in the first instance that it was a bug instead of being asked to take time to try and correct something that can only be fixed by your developers! I always appreciate the help and support from yourselves, but I’ve had it on a few previous occasions where I’ve been asked to try various ‘fixes’ for things that have already been reported as bugs, which is time I could have spent working on the website and I’m sure you could have used the time elsewhere too! Is there a page or area which lists known bugs?

Thank you @Acumed for making me aware that you have already reported this and is a known bug, otherwise I’d have wasted more time going back and forth asking for a workaround!

Cheers

Hi There,

Thanks again for the update!
I am really sorry on behalf of @Prasant as he might have missed checking the issue tracker.
I have escalated the issue again to our development team, they will have a quick update on it.

Thanks for understanding.

1 Like

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.