Forum Replies Created
-
AuthorPosts
-
All of your plugins (bar one) are at least 1 and some even 2 years old
and the wppizza plugin itself you are using is also about 7 month out of dateI would suggest you update your plugins to start off with
also :
what wppizzq version
(and versions of related wppizza plugins)what other plugins are you running ?
any custom coding of some sort ?>Have you ever had such a similar case?
nowhen does this happen ?
when you install the plugin?
when you update the plugin ?
at some other random time ?you’d have to write some javascript to show/hide things
there are plenty of classes you can target(and you’d also have to trigger clicks to select/deselect if – for example – someone selected a saladsauce but then changed his/her mind and wants pommes instead )
maybe it would be a better idea to actually create some sort of “burger menu” to start off with.
something along the lines of the “breakfast example” herehttps://demo.wp-pizza.com/wppizza-add-ingredients/our-menu/user/
one more quick question for you please:
was the preorder plugin an update from an earlier version , or did you install v2.5.2 to begin with on that site ?
thanksPS perhaps check the other strings in that shoppingcart section too
my guess would be that for some reason (i will check if i can reproduce this somehow)
your localization strings in wppizza->localization got overwritten with the settings from the preorder plugin)so if you go to
[www.yoursite.com] /wp-admin/edit.php?post_type=wppizza&page=localization
and scroll down to “Shoppingcart” you will find this there , instead of the defaultsso if it says
<span class="wppizza_cart_preorder">currently closed – pre-orders only</span>somewhere in one of those text boxes, simply overwrite this with “currently closed” (or whatever you want to say )let me know if my assumption/guess is correct please
that’s typically down to some broken/invalid css before that stops any declarations after being applied
a quick – working – example (as mentioned, mileage may vary, and the caveat regarding function name remains)
/* get orders */ $orders = wppizza_get_orders(); /* get template */ $template_type = 'print'; $template_id = 0; /* parameters of template print template id 0 */ $template_parameters = get_option(WPPIZZA_SLUG.'_templates_'.$template_type); $template_parameters = $template_parameters[$template_id]; /* get markup for each order */ foreach($orders['orders'] as $order_formatted){ $order_for_template = array(); $order_for_template['sections'] = $order_formatted; $markup = WPPIZZA() -> templates_email_print -> get_template_email_html_sections_markup($order_for_template, $template_parameters, $template_type, $template_id); }i would strongly suggest you start here in that case
https://docs.wp-pizza.com/developers/?section=function-wppizza_get_ordersget the template parameters (in this case print from the print templates id=0 and assuming it’s set to be using html format for your purpose)
$template_type = 'print'; $template_id = 0; /* parameters of template print template id 0 */ $template_parameters = get_option(WPPIZZA_SLUG.'_templates_'.$template_type); $template_parameters = $template_parameters[$template_id]; /* get the html markup $order formatted will be the order(s) you get from the wppizza_get_orders() functions so the below should be in a loop */ $markup = WPPIZZA() -> templates_email_print -> get_template_email_html_sections_markup($order_formatted, $template_parameters, $template_type, $template_id);mileage may vary, and not tested as such, but something along these lines.
the next version of WPpizza will probably have a global wrapper function that replaces the
WPPIZZA() -> templates_email_print -> get_template_email_html_sections_markupwith something that is easier to use (and i would strongly recommend to use it once it’s implemented as theget_template_email_html_sections_markupreferred to above *might( well change at some point in the future as it’s really only an internal function, but I’m just mentioning it here. just do not rely on it )sorry, but only plaintext will be stored in these fields
I dont actually even understand why html would be useful there I must admityou’re welcome. thanks for letting me know about the issue
>I See you also fixed the Bug…
yupJust for your info: it’s an issue of how javascript handles that character when uppercasing/capitalising it , not the plugin as such.
ok, as of v4.0.22 of the postcode plugin, the “ß” character now gets automatically converted to ‘ss’ when saving and using the “autocomplete” / “Show as Textbox instead of dropdown ?” option.
so, update the plugin and save your “streets” once.
I would think this all works thenthere could be more issues after that’s fixed of course , but this is definitely one of them (and perhaps the only one , we’ll see)
So, just to keep you updated, the problem is the “ß” character (ä, ö, ü are fine). as it gets converted to “ss” on the frontend/autocomplete
as that does not match the original entry there are no matches between what’s entered in the backend and selected in the frontend so it will never allow selectionso at least we know now where exactly the problem is. i just have to find the place now where this conversion happens in the chain of events to be able to fix it
again, i’ll keep you updated when i know more
This reply has been marked as private.Ok, I cannot see anything obvious (but you should nevertheless consider setting your php save path though)
the only way i can really find out what the issue may be is if i can take what you have there exactly apart
so if that’s acceptable please do the following :
install duplicator https://wordpress.org/plugins/duplicator/
create a (full) package , then zip up this package and the related install.php and make it available for me to download somewhere so i can have an exact copy of your site here i can investigate without having to touch your install -
AuthorPosts