Forum Replies Created
-
AuthorPosts
-
please send me an email to dev[at]wp-pizza.com as i will have to ask you for some credentials
do NOT post them here – even as private reply – as the original poster will also have access to it !have you (or anyone else for that matter) tried the link i posted ?
first of all, why do you need users to be registered anyway ? (if that’s what you want , then that’s your prerogative of course, but this will not be native to wppizza – as i already alluded to at length elsewhere on this forum)
secondly, having had a quick look on some german law sites, double-opt in ONLY seem to be required for newsletter subscriptionsthis is not what wppizza does so can’t see the issue in the first place on that front
(again, am not a lawyer and might be completely wrong of course, just saying)wppizza simply uses the way wordpress does registrations (i.e people select “register” and they get an email where they have to set their password)
perhaps there is a way one can make this an option to double opt in – i’ll have a think but i can assure you it’s not imminent
i am of course not a lawyer, but i am not sure whether you actually need double opt in here anyway as you are not subscribing to any newsletter but simply add your email to an order you make …apart form that here’s an
— abbreviated quote from one of the wordpress core developers ——
Many regulatory issues are left up to 3rd parties simply because they’re not used by everyone and the regulations are vastly different in different places.
……
It’s also the same reason that the eu cookie law isn’t directly handled by core and remains a hook able feature.
——— end quote ——-furthermore, why does it mean “no guest checkout” ?
pizza.de (for example) does not seem to have any issue with me just typing in my email address when ordering
should it not in fact be ONLY guest check-out ?
i don’t know the full story of course but it sounds to me like your server people need to do their homework (ptr , dmarc, whatnot records)
cant see why this should be your issue (and most certainly not wppizza’s issue)surely , that should be blocked at server level …
not sure why this would be a wppizza issue (or how wppizza should/could solve this )but feel free to expand as to what you would want wppizza to do
oh, i might have misunderstood.
perhaps you meant in the place the theme provides to add css…anyway, as long as it works for you , we’re all happy :)
>I did it right in the theme.
why would you do that ? next time the theme updates your dots might well be backi can assure you wppizza does not do dots (red or otherwise) but your theme does
(it adds them to li elements as backgrounds)the “old” wppizza just overwrote them 3.x does not (but the next version will. i might as well put this overwrite back in)
in your particular case it’s – most likely – that you are still using an old version of the “dbp” plugin
did you read and follow the upgrade instructions ?
http://docs.wp-pizza.com/getting-started/?section=upgrade-v2-x-v3-x>WordPress automatically upgraded all my client’s websites wppizza plugin
no, wordpress does not do that . but other plugins, themes or custom scripting mightFor over a year now – there was a notice in the wppizza plugin warning people about NOT to simply update the plugin when version 3 comes out. Then – when version 3 was made available – the warning got even bigger and redder. (Not to mention that it is also clearly said in the changelog) As well as a link to the upgrade instructions
Don’t get me wrong, I can understand why people do autoupdates and up to a point they have their merit – if updates are updates for micro or perhaps even minor version changes. Autoupdating major versions however is simply a very bad idea. This is not only the case for wppizza but for any plugin or theme.
Back to the issue at hand though:
Other than restoring a backup , there isn’t any way back from 3.x to 2.x
however, you can try re-saving each of your settings pages to start off with, also enable debug and check your debug.log filei would first of all recommend to at lest read the upgrade instructions once or twice
>now works perfect for me,
good>Thank you for your prompt and effective help.
no problem, thanks for flagging the issuecan you guys please update to 3.0.3 and let me know if this fixes it in your case(s) ?
thanksi’ll post back here when i know more
i have one more user that has the same issue. as i have access to his site i will try to get to the bottom of it tomorrow (i assume you are using wppizza 3.x ?)
if i find the issue on his site – and am able to fix it – i will of course update the plugin asap which in turn should fix your issue just the same i would have thought
just bear with me for a day
after a bit of digging :
can you try this :
http://www.techextensor.com/fixno-publish-but-submit-for-review-button-displayed-to-site-admin/(assuming you know what Phpmyadmin is and feel comfortable with doing so )
the plugin – updated to v3.x or not – does not really do anything as such to the post table (other than storing the products there) so cannot see how it would cause this issue, but let’ see if we can fix it in the first place with the above suggestionone more question: is this only the case for wppizza products or generally for any/all other posts pages or woo products too ?
ok, i’ll see if i can reproduce this somehow. might have to ask you for some login credentials or a duplicator package (https://en-gb.wordpress.org/plugins/duplicator/)
i’ll do some digging first
-
AuthorPosts