define('WP_DEBUG', false);
REPLACE this with (or if it does not exist simply add the below)
define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);/*this should NEVER be true for production sites*/
Note: this MUST be before /* That's all, stop editing! Happy blogging. */
Which will generate a file “wp-content/debug.log” if and when any errors are encountered.
Check this file for errors if you need to find out where things might go wrong
Note that in many cases a lot more information/help is available in the help screens of the plugin
If you see some “500 Internal server errors” in there, check your server error log. In many cases these are caused by uploading a plugin with the wrong permissions – especially if you add plugins by ftp instead of using the standard wordpress plugin installer. You should also aim to fix any other javascript errors you may have, although some might be more problematic than others
If you have issues with WPPizza – or WordPress in general for that matter – I would highly recommend the following resource(s) to narrow down where your issue(s) might be
As I could not say this any better, forgive me for simply providing the links above. I would, however, especially recommend the “Troubleshooting Plugins” section on the perishablepress.com link ; about 2 thirds down on that page.
Of course, if you have followed the recommendations on those pages without being able to solve your problem and still have issues with WPPizza, please get in touch via the usual channels (forum, contact form, emails)
]]>Warning: session_start(): Cannot start session when headers already sent in [site-path]/wp-content/plugins/wppizza[xyz]/[some-file] on line [some-line]
or
Warning: cannot modify header information - headers already sent by [site-path]/[some-dicetory]/[some-file] on line [some-line]
The problem is that either:
Although the session start warning references a wppizza file, this is *not* in fact a wppizza error/fault (as confusing as this might seem, admittedly) but it points to some other file or plugin outputting content before it should do.
If it’s a “cannot modify header information – headers already sent by” instead, it typically also tells some file and line number.
:
:
PS | FYI: Wppizza uses native php sessions – extensively – that simply will not work if other scripts/plugins/themes output content where they should not.
]]>To do so go to: WP(WordPress) -> Settings -> General
and enable Anyone can register
If you are using a multisite setup you will have to do this in the network settings:
WP(WordPress) Network settings -> Registration Settings -> Allow new registrations : User accounts may be registered
Furthermore, please ensure the dedicated "email"
field in Wppizza -> Order Form Settings
is enabled and set to be required (to allow the user to receive his/her password for a newly created account)
This is the field that has the hardcoded, non-changeable “Type / Validation” of “email”
Note: the “continue as guest / register” options will only show up if the user is NOT logged in already (for obvious reasons), else a simple checkbox that allows to “update my details” will be displayed.
]]>In 99.99% of cases this is due to the session save path (php.ini) not being set correctly or at all and/or the directory not existing or not being writable.
Typically this would read
session.save_path = "/tmp"
or
or
session.save_path = "/var/lib/php5"
or similar in your php.ini.
session.save_path = "/var/lib/php5/session"
Refer to the php manual for more details regarding session setup
You should speak to your host / server administrator to get this fixed and to make sure the appropriate path is set with the correct permissions. WPPizza will not work without php session support.
]]>WPPizza->Gateways
and “Completely disable online orders” is not checked in WPPizza->Layout
]]>WPPizza requires mySql 5.5+ – (see requirements: https://wordpress.org/plugins/wppizza/ – In fact, WordPress itself recommends 5.6+ )
If the above is the case, update your version of mySql or get your host to update it for you. Once you have done so go to "Wppizza -> Tools -> Maintenance [Tab]"
enable/check "Update order table"
and save once.
To enable, either add this line to the functions.php of your theme;
add_filter('widget_text', 'do_shortcode');
,
use one of the wordpress plugins available that do this
or contact the theme developer and ask him/her to enable it
]]>WPPizza - Categories
in the admin side of things even though they are happily showing up in the frontend.PHP Notice: Undefined offset: [abc] in [plugin-path]/wppizza/classes/class.wppizza.categories.php on line [xyz]
To fix this, do the following:
it should all now show up again as it should and any new php notices to that effect should disappear
]]>For a possible solution have a look at
https://techubber.blogspot.com/2017/09/how-to-fix-wordpress-plugin-update-failed-solutions.html
and generally
https://www.google.com/search?q=Update+Failed%3A+Plugin+update+failed
of course.
Some security plugins will also apply settings that would stop this process to work.
Therefore, if you are using plugins like wordfence or similar, or things like “System Tweaks” in iThemes, try de-activating those (temporarily) and see if the update works then.
(If it does, simply re-activate the aforementioned plugins/settings after your successful update)
If you are using settings in an .htaccess file to restrict siteaccess by implementing some sort of authentication to access your site, disable this authentication requirement then try to update the plugin(s) and subsequently re-enable authentication as appropriate.
If none of that helps, you can also do the following:
(It is always advisable to make a full backup of your site first if things should go wrong for some reason !)
[wppizza -some attributes-]
on it)
make sure your theme (or one of your plugins) does not use an old version of jQuery (some themes/plugins override the version that comes bundled with wordpress – no, i don’t know either why they would do that)
If that still doesn’t help, you might have to adjust the CSS (see Modify Css)
If you have problems, send me a link to your site I’ll have a look…
]]>