Forum Replies Created
- AuthorPosts
-
Hi Olly
I spoke with the theme developer and his response was this. I suppose just let me know your response.This is happening because the plugin loads its styles on all pages instead of loading it on pages where it is used.
Woocommerce provides a function called is_woocommerce which allows us to avoid that. I couldn’t find an equivalent function for wppizza plugin though. Try asking the plugin developer about this and I can help with the code if such function exists.
I tried using his method but it still affects other elements like datepicker:
You can use the jquery-ui.css from the above link to try it yourself.
Is there any way to tell the themeroller CSS to affect only the WPP spinners?
Thanks that all makes sense and I’ll do my best to make progress over here. (and yes get some rest!)
Thanks Olly. There was nothing like the theme’s default in drop down, so I currently have “I have my own style” selected. There really is no style now associated with those counter boxes.
So at this point I need to ingest a style for them (and it seems the input fields on the order form?)I’d like to be able to use my theme’s default here, but it does not seem like it’s naturally working.
Thanks. Got it.
You are correct, the server admin found that issue and fixed it.
Can you tell me where the element “wppizza-delete-from-cart” is coded? (the “X”) In v2 it was in the default css and this time I’m spinning my wheels to find it.
Hello Olly–
I did end up rebuilding the menu and settings freshly on the new site (well I’m still in the process of.) I figured it would be the best way to get a tour of the stuff added/changed in V3. Everything is so clean! Im loving the wppizza.default.css file– especially when compared to the mountain of bits that was the v2 file;)
That’s exciting to hear. I noticed the customer tab and read a bit about it. Looking forward to life in v3. Thanks!
I failed to mention–
V2 resides on a different site than the one V3 will be created on. I did previously read the v2 > v3 upgrade paper. So I need to know if there is a way to move the plugin (without breaking the destination site!)
Then I can upgrade according to the paper.I’ve read that in the past and just re read it now and agree with it. I personally avoid registration wherever I can.
To be clear, we do not force or even allow registration.
Maybe I’m using the wrong verbiage and it now seems clear customer screen is intended for an entirely different purpose.I’m just hoping I can somehow filter orders on the backend either by name or by email address and see a order history.
That is correct. Most of our guests just stay overnight and we typically do not get repeat customers like a restaurant would.
On the check out page, guests simply enter their name, email address and room numbers (required info) and that’s it.
I hope in some iteration wpp might recognize a unique name as a unique customer.Got it.
Many thanks.Can you tell me where that shopping cart icon is coded?
I’ve spent the better part of the day looking for it and now I’m just spinning my wheels.
Thanks!what do I need to add before this line for it to take affect in the default layout:
.wppizza-article-size:after{content:url(img/cart-black-12-12.png);position: relative; top: 2px; margin:0 3px;}
It’s in
themes > x-child > wppizza > templates > markup > loopSeparately, can you tell me the name of the file where I can update the shoppingcart image?
I can’t seem to find where to replace the shopping cart icon on the categories pages. My goal is to change the icon to a png that I created.
I found:
.wppizza-article-image-placeholder:before{content: “\f306”; font-family: “dashicons”;color:#bebebe;font-size:62px;}
in wppizza.grid.css.php but of course this only affects the grid layout.
where can I find the similar code for the default layout so I can change out the shopping cart icon.
In v2, it was in wppizza-default.cssAlso, posts.title.php still is not working in the child theme tree.
Thanks
I deleted it when I ran into that backpaging issue. I’ll add it back now.
posts.title.php
is the current problem. The instance in the child theme doesn’t seem to be effecting the site.This reply has been marked as private.Hi Olly–
I’m copying the CSS/php files as instructed and placing them in the child theme’s dir using the original file structure and the changes are not effecting the files.
In your comments in wppizza.custom.css it explains that “This file will always be included after the main wppizza css”
So the obvious question is where can I place these files so they actually do take precedence?posts.title.php
wppizza.cssI am placing each of them in their appropriate structure.
So I reinstalled and things are a go.
Got to say that I’ve LOVING all the new functionality and gadgets in 3. Also, thanks for the comments in the CSS. Everything is so clean — makes the tad bit of customization we need a breeze.
- AuthorPosts