Please help!!!
The Vantage Theme Im using in me website is caussing White Screen of Death!
I disabled all the plugins and also the theme, and the web was back on.
I then tried to re.activate Vantage theme and it want blank again.
Help please!
Vantage theme causes White Screen of Death
This is our free support forum. Replies can take several days. If you need fast email support, please purchase a SiteOrigin Premium license.
Hi gis
Sorry to hear about this.
Have you tried installing a fresh copy of the theme? You can download the ZIP file from the link in your order confirmation email. You can re-send that email to yourself if needs be from here: https://siteorigin.com/orders/
Just went over your other thread: https://siteorigin.com/thread/add-paypal-buttons/. To confirm, the white screen happened during the editing of theme files? If that is the case then re-installing the theme would be best way to go.
Hi:
I re-installed a fresh download of the theme and it still has problems, such as:
I cannot change the short description in the general settings ,por example.
The screen turns white again and nothing happens.
I have to click return, but the change I was trying to make is not applied.
Help please!
Thanks again.
Glad to hear the re-install resolved your main challenge.
1. Vantage unfortunately doesn’t render the tagline. Try using Appearance > Theme Settings > Home: Support Text or the header widget area at Appearance > Widgets.
2. This sounds like a plugin conflict. Please temporarily de-activate all non-SiteOrigin plugins and re-test. If the issue is resolved then re-activate your plugins one by one, each time checking the problem.
Hi:
The website is working quite ok but I still have some problems with my theme.
I download a plugin called Theme Check and I ran a check on Vantage Premium (my theme).
It come out with this:
WARNING WP_DEBUG is not enabled! Please test your theme with debug enabled before you upload!
REQUIRED: Found a Customizer setting that did not have a sanitization callback function. Every call to the add_setting() method needs to have a sanitization callback function passed.
RECOMMENDED: No reference to add_theme_support( “custom-header”, $args ) was found in the theme. It is recommended that the theme implement this functionality if using an image for the header.
RECOMMENDED: Tags: is either empty or missing in style.css header.
INFO: premium/extras/customizer/customizer.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 10: $google_web_fonts = include ( dirname(__FILE__) . ‘/google-fonts.php’ );
INFO: inc/widgets.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 93: $icons = include ( get_template_directory() . ‘/fontawesome/icons.php’ );
Line 94: $sections = include (get_template_directory().’/fontawesome/icon-sections.php’);
INFO: inc/menu.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 52: $icons = include (get_template_directory().’/fontawesome/icons.php’);
Line 53: $sections = include (get_template_directory().’/fontawesome/icon-sections.php’);
INFO: iframe was found in the file premium/extras/share/share.php iframes are sometimes used to load unwanted adverts and code on your site.
Line 83: <iframe allowtransparency='true' frameborder='0' scrolling='no' src='<?php e
INFO: extras/metaslider/metaslider.php The theme appears to use include or require. If these are being used to include separate sections of a template from independent files, then get_template_part() should be used instead.
Line 59: include_once($lf);
Is there something you can do to help me fix this?
Thanks again.
The Theme Check plugin is aimed at developers working to get their theme’s approved on the directory, it’s not really aimed at a consumer level, hence the technical nature of the output it produces.
1. A developer would be working in a development environment. You aren’t testing the theme and are working on a live site so WP Debug shouldn’t be turned on. A developer would have it on for testing in a development environment, on a website not live to the public.
2. I’ll take a look at the Customizer REQUIRED item that was initially mentioned. If necessary I’ll log a bug report on our side.
3. The RECOMMENDED and INFO items are just that, recommendations or points of info. Themes with RECOMMENDED or INFO still pass the review.
Just a quick update on point 2. We are sanitising but not at the instance that the plugin is checking, it’s happening at another point. So you’re safe. This point will be addressed in a future update.