Forum Replies Created
-
AuthorPosts
-
cannot see the minicart there being used/enabled ?!
(mobile view or not)this sounds more like your theme is hiding certain things in mobile view as the plugin does not do that
unless you are telling it to using the available (shortcode) attributes if adding the minicart by shortcode instead of using the widget
(i cannot say any more without a link to your site I’m afraid)>/wppizza/markup/cart/cart.container.php
>/wppizza/markup/loop/theme-wrapper.phpthose are – already – v3 files…
must admit , i don’t really understand what the problem seems to be here …sorry, but i don’t think i understand the question exactly (or actually the requirement as to why you would need this )
PS: this sounds like you have edited corefiles
In case this is what you have done please note: there is no support for editing core files and is entirely at your own risk (and is never a good idea in any case because that’s what filters and actions are for)what file exactly did you customise (and how)
re 1) the button will only show up when there are ingredients already added to an item that can be edited.
however, i kind of agree with you it should probably also be there anytime adding ingredients is enabled for an item
i’ll see what i can do in an updatere2)
# When you set up “Custom Groups” and dont check “Sort by price first [will override any drag and drop sorting you may have done]” then the sorting will be not sorted by price,
– err, yes. that’s what it does (and says) ?!#even when you selected it: Ingredients > Options > “*Added* ingredients display options” > by price
– Note: it says *Added* ingredients there !!# “Sort by price first [will override any drag and drop sorting you may have done]”
– this works just fine from what o can seeall in all though as i do not know your setting and you have not provided any links or screenshots that ‘s all i can say here
PS: Actually, the same goes for the custom opening times it seems…
same applies: will be fixedi can actually reproduce this here.
i’ll fix it in the next update (so they won’t disappear when you update) – should be reasonably easy to do
thanks for letting me knowi’ll check and get back to you
23 November, 2017 at 2:34 pm in reply to: Zip / postcode field doesn't work for UK as it's a numeric field. #33098ok
a couple of things for future reference (and thinking out loud for a bit here too)
– although there’s no checkbox option to turn this post/zipcode validation off (as this really is a security validation you should have enabled to combat fraud) if one really wants to disable this (for whatever reason), there’s a filter included that could be used to disable this verification like so
add_filter('wppizza_gateway_stripe_filter_vars', 'myprefix_stripe_filter_vars'); function myprefix_stripe_filter_vars($vars){ unset($vars['zipCode']); /* or alternatively */ $vars['zipCode'] = 'false'; return vars; }– hmm, i wonder about the following though (not a too common scenario i would think but not impossible either):
what happens if i have a UK credit card and bank account. I then move to another country – let’s say Spain – and change the address associated with this account/credit card – as i would have to.
therefore my postcode changes from something like ‘SW6 1AB’ to ‘071234’ ….I would have thought it’s still a UK credit card (UK Bank), but the zip/postcode has a different validation structure now.
Admittedly, the chances are also quite good that i would also have “proper” credit/debit card associated with a spanish bank and postcode, but still….or maybe stripe is clever enough to be able to work out this kind of thing too. (the validation rules in the gateway implementation are set by stripe , not by me btw)again, just thinking out loud here…and it’s probably still a lot safer to insist on postcodes that match the card-country even if it means perhaps loosing a customer or two (though – as mentioned above – the chances are they will also have alternative ways to pay)
23 November, 2017 at 1:22 pm in reply to: Zip / postcode field doesn't work for UK as it's a numeric field. #33093hmm, I don’t think that’s true actually (but feel free to prove me – and Stripe – wrong)
according to stripe docs
https://stripe.com/docs/stripe-js/reference#postal-code-formatting
Postal code formatting
The card Element automatically determines your customer’s billing address country based on their card number. Using this information, the postal code field validation reflects whether that country uses numeric or alphanumeric-formatted postal codes, or if the country uses postal codes at all. For instance, if a U.S. card is entered, the postal code field only accepts a five-digit numeric value. If it’s a UK card, an alphanumeric value can be provided instead.so it entirely depends on the card no you are using – well, according to their documentation anyway.
if you have evidence to the contrary i’d be glad to hear it and pass it on to / have a word with the guys at stripejust a few notes:
– generally i keep css changes to a minimum and they are very targeted and not just some blanket change to all things
– i would suggest you also run some sort of staging/test server if you want to see what changes have been made before applying them to a live site (this is probably generally a good idea regardless)
– there are plenty of programs (and probably WP plugins too) that would let you run a comparison on before/after files to show you exactly what the differences are
– in that particular update “.wppizza-article-responsive .wppizza-article-content” was not even touched as such (it was only some .wppizza-article-sizes>ul>li:before, .wppizza-article-prices>ul>li:before {content:”} that was emptied as some themes added some blanket dots or whatnot before the prices)
– if you had to re-apply your css changes (though i am not sure that was the case here, but it might have been, so am just mentioning it ) you should consider using a child theme and / or using the provided ways of overriding wppizza css (as those customisations will always be read after the included css and will therefore have priority if distinctly targeted )
again, I’m just mentioning this for completeness sake and might not at all have been the issue herein any event though, glad you got it sorted again for your requirements
quick update: now enabled/doable with wppizza v3.1.6
but theme template edit/copies will be required – please see docs
https://docs.wp-pizza.com/developers/?section=wppizza-markup-search
https://docs.wp-pizza.com/developers/?section=wppizza-markup-search-search-php@claudio
a) please start your own topic
https://support.wp-pizza.com/topic/forum-rules-read-me-before-posting/b) quote:i wanna disable the SMTP in my site.
who’s stopping you | what does that have to do with wppizza as such ?according to this documentation on wpengine: https://wpengine.com/support/wpengine-ecommerce/
simply renaming your order page to cart, checkout, or check-out (assuming you are using permalinks presumably) should also stop the checkout/order page from being cached (in case someone else comes across this thread /topic here)
update to the above:
it transpires there is no documentation I wrote on that subject , simply because there are no provisions for this (yet)i spent most of the day today trying to find a way to do this automatically in some way shape or form to integrate this without having to edit/mess around with theme templates.
Alas, there does not appear to be a way to do this without editing theme files (similar to the single page templates in the link i posted above) or, to be more accurate, I could not find any universally usable way to do this without the need to edit theme (search) templates.
Note: this kind of makes sense up to a point , as themes should have control over layout and plugins should add the functionality. Problem being here that wppizza is a bit of a hybrid on that front.Offshot being, I have to write and add a function or two to the plugin and add some documentation to the docs regarding how to edit/amend the search template
I am fully committed to do this, but it will take a day or 2 to do to add to the plugin and writing the docs
please bear with me
this is – most likely – a (wpengine in this case) caching issue
please see here
http://docs.wp-pizza.com/faqs/?section=using-a-cache-pluginactually , i just tried this and although you probably want to create a single.php as outlined above (as your result would link to a single item )
my guess is you also want the item to be displayed as “normal” so to speak (i.e with clickable prices etc in the searchresults)i assume this is indeed doable and i *believe* i wrote the documentation for this somewhere, but need to find it (and if it does not exist yet , i’ll write it if this sort of thing is possible )
but you’ll have to bear with me for a bit on that one
you need to create a single.php page as described here
http://docs.wp-pizza.com/developers/?section=wppizza-markup-single-single-php(although this is mentioned in the widget, the link i put there – which is meant to point to the page above – is actually wrong, i need to fix that )
-
AuthorPosts