August 5, 2017 at 12:08 am #7491
I am having problem with my blog page, probably because my PageBuilder SiteOrigin is desactivated. I found a better page builder for my project and that’s why I need to keep PageBuilder off. Now my blog page is all black. How do I fix this? Is it possible to fix keeping PageBuilder off?
JessicaAugust 5, 2017 at 5:21 am #7492
That shouldn’t be any problem. If you were previously using a Post Loop widget for your Blog page you’ll now need to assign your blog page via
Settings > Reading > Posts Page. Has that been done?
If this doesn’t help, please, share a link so I can take a look.
ThanksAugust 7, 2017 at 5:07 pm #7493
Yeah, i have done this but my page looks like this: https://drive.google.com/open?id=0B0ujY1xhs_qbSVY3YTF6Zjdzb3c
When I activate SiteOrigin plugin the page works. Maybe I have a problem with my archive.php. I don’t know.August 7, 2017 at 5:39 pm #7494
Thanks. I’ve never heard of this happening before. To find out where the issue lies:
1. Deactivate all plugins except for Page Builder by SiteOrigin. Does the issue persist?
2. Activate a default theme like Twenty Seventeen and Page Builder by SiteOrigin. Does the issue persist?August 7, 2017 at 5:40 pm #7495
Have you directly edited theme files at a code level?August 7, 2017 at 6:10 pm #7496
No, I am using a child theme and I didn’t change the code.
If I activate PageBuilder my blog page works great. The problem is: I need to desactivate, I don’t want to use the SiteOrigin plugin, because I am using another page builder (elementor) and when both are active there is a conflict. My blog page works ONLY with PageBuilder by SiteOrigin.
I think the problem is in the archive.php because the code has this line “get_header(); ?>
<?php if ( siteorigin_page_setting( ‘page_title’ ) ) :”
I’m just guessing. If you want to, I can send the code.
Sorry if my english is bad 🙁August 7, 2017 at 6:13 pm #7497
We can try to work out the issue later but it’s best to make big changes in the beginning of troubleshooting. So step 1. Switch to the parent theme, does the issue persist?
The reasoning behind my previous advice was that if the problem did not occur with ONLY Page Builder by SiteOrigin activated then we would know another plugin is the issue.
The code mentioned is not the issue. That code refers to the SiteOrigin Settings Framework, not Page Builder by SiteOrigin.
So, step one, switch to the parent theme, deactivate Page Builder by SiteOrigin, does the issue persist?
If the issue persists. Stay with the parent theme activated and deactivate ALL plugins in one go. Does the issue persist?August 7, 2017 at 6:18 pm #7498
Phew, sorry, part of my advice did not make sense, long day. Let me try that again:
1. Switch to the parent theme. Does the issue still occur?
2. If the issue still occurs, deactivate all plugins in one go, does the issue still occur?
That will give us some idea of where the problem is coming from.August 7, 2017 at 6:22 pm #7499
I have done what you said and persist. All plugins are deactivated and I am in the parent theme, same problem with the blog page.
My Chrome says this when I press ctrl+u
<b>Fatal error</b>: Uncaught Error:  operator not supported for strings in C:\xampp\htdocs\wordpress\wp-content\themes\ultra\inc\panels-lite\inc\css.php:27
#0 C:\xampp\htdocs\wordpress\wp-content\themes\ultra\inc\panels-lite\inc\css.php(65): SiteOrigin_Panels_Lite_Css_Builder->add_css(‘#pg-home-0’, Array, 1920)
#1 C:\xampp\htdocs\wordpress\wp-content\themes\ultra\inc\panels-lite\panels-lite.php(299): SiteOrigin_Panels_Lite_Css_Builder->add_row_css(‘home’, 0, ”, Array)
#2 C:\xampp\htdocs\wordpress\wp-content\themes\ultra\inc\panels-lite\panels-lite.php(389): siteorigin_panels_lite_generate_css(‘home’, Array)
#3 C:\xampp\htdocs\wordpress\wp-includes\class-wp-hook.php(298): siteorigin_panels_lite_css(”)
#4 C:\xampp\htdocs\wordpress\wp-includes\class-wp-hook.php(323): WP_Hook->apply_filters(NULL, Array)
#5 C:\xampp\htdocs\wordpress\wp-includes\plugin.php(453): WP_Hook->do_action(Array)
#6 C:\xampp\htdocs\wordpress\wp-includes\general-template.php(2589): do_action(‘wp_head’)
#7 C:\xampp\htdocs\wordpress\wp-content\th in <b>C:\xampp\htdocs\wordpress\wp-content\themes\ultra\inc\panels-lite\inc\css.php</b> on line <b>27</b><br />August 7, 2017 at 6:25 pm #7500
Ok so final step:
With all plugins deactivated, switch to a default WP theme like Twenty Sixteen, is the issue resolved? If so, we know it’s the parent theme. If this is the case, try deleting the parent theme, reinstalling it from Themes > Add New > search for Ultra and install then activate. Does the issue persist with a fresh copy of the parent theme installed off the theme directory?August 7, 2017 at 7:01 pm #7503
How’d that go?August 7, 2017 at 7:06 pm #7504
Twenty Seventeen installed and working. I removed both parent and child themes and installed ultra again. The issue persist 🙁August 7, 2017 at 7:13 pm #7505
Ok, thanks. Sorry about this, I haven’t encountered or had a user encounter this error before. It’s possible there is something about your XAMPP stack that isn’t working with a part of the theme. We will most likely find this problem doesn’t persist once you move to a live server.
I will also investigate this error and resolve as soon as I can find a work around/solution.
For now, let’s do this:
Plugins > Add New, install a super useful plugin called Code Snippets.
2. Snippets > Add New, name it as you’d like and in the snippet body, insert the following:
define( 'SITEORIGIN_PANELS_VERSION' , 'dev' );
Finally, Save Changes and Activate. You have to click the button with activate in it as you can save without activating.
OR in your child theme functions.php file, insert the following:
define( 'SITEORIGIN_PANELS_VERSION' , 'dev' );August 7, 2017 at 7:22 pm #7506
Thank you! Now it’s working. If you find what’s the issue, tell me 🙂
When my site is online, I will test to know if the problem is with my xampp.
August 7, 2017 at 7:24 pm #7508
- This reply was modified 11 months, 2 weeks ago by Jessica.
Thanks for your understanding. I’ll let you know as soon as I know more. Please, let me know how it goes on the live site.
Chat soon 🙂
You must be logged in to reply to this topic.