Forum Replies Created
-
AuthorPosts
-
if using the default theme its
.wppizza-article-default .wppizza-article-size:afterif using the grid theme its
.wppizza-article-grid .wppizza-article-size:afteretc (reason being that you will be able to have different layouts for different pages if you want)
there is a min css (wppizza.css) that applies to all and selective overrides depending on layout used
if you want to overwrite things, copy custom.css as outlined earlier somewhere i believe to your child theme and overwrite it as needs be (or use your theme’s inline css option)
you lost me. it’s pure css ?!
.wppizza-article-size:after { content: "\f174"; font-family: "dashicons"; font-size: 120%; position: relative; top: 2px; margin: 0 3px; }wppizza v2x only- something like this perhaps:
add_action('wppizza_gateway_do_order_details', 'my_js_output', 10, 2); function my_js_output($orderDetails,$id){ print"<script>/* echo your js */</script>"; }>I saw few of other member here had same problem
true, but i have no idea how they solved it (if at all)
the cloudprint plugin simply sends the template to google cloudprint.
as i said, what the/any printer makes out of it i have no control over sadlyplease use your bowsers element inspector to see applied css declarations
generally speaking, in 99.9% of cases , there will not be any need to mess around with these/any files as there will be plenty of filters (but as mentioned , documentation is to come)
your theme already seems to provide an option to overwrite css without having to mess around with files
themes > x-child > wppizza > templates > markup > loop
should be
themes > x-child > wppizza > markup > loop>name of the file
none. it’s css. overwrite it as necessary
.wppizza-article-size:afterPS: if your printer adds margins or something , than that’s something i have no control over and you’ll have to speak to the printer manufacturer
i dont know which version of the cloudprint plugin you are using
generally though (with reasonably recent versions)
you select the template you want to use in the plugin and then edit that template accordingly (wppizza->templates)there is no file that needs editing
why would you be looking at .wppizza-article-image-placeholder
if you want to do something with the shoppingcart image ?>posts.title.php still is not working in the child theme tree.
works 100% . i can only assume you put it in the wrong directoryThis reply has been marked as private.This reply has been marked as private.>FYI – I had an instance of WPP “crashing”
that’s actually down to backpaging to an order that has already been dealt with so to speak (i’ll spare you the details).
regardless, in the version i have here (i’ll make that available in a day or two) that should also be dealt with (would only affect COD orders )>I am placing each of them in their appropriate structure.
without actually being able to see the structure you created, i cannot comment
(better still, including a link to that site)>together with a registered SSL certificate
not strictly necessary with the omnikassa/rabobank gateway of course, but never a bad idea and highly encouragedin v2.x no, unless you do/add this yourself / edit the cart template and add the js as required
in 3.x this will be the default (using arrows though)if you kill the orderpage, you have no input for anyone to type in their order info
so you need to add that info to however you add it using your own thing>Can these files be used in their CURRENT form in v3
not really, no (the css – up to a point perhaps – but the others will not exist anymore)
and modifying emails should use the emails templates under wppizza->templatesdocumentation is being written as we speak but – as you might imagine – is quite a big undertaking therefore it will stay in beta until there’s a documentation that goes with it
anything else will just end up being a messFurthermore, software in general moves on and what is working today might not work at some point in the future . even wordpress itself or other wordpress plugins/themes you may be using might interfere with each other and stop things working or throw errors because they themselves are not being updated by the user or plugin/theme developer to keep them working with advances in software (php for example)
Noone will be able to give you a guarantee that it will work 100% all the time as there are many parts and 3rd parties involved , all of which may get changed by whoever is responsible for maintaining that part at any time.
for example, if Omnikassa/Rabobank (i dont know what “other” company you were referring to) simply change their API at some point than there is a chance it might not work anymore (though once i get informed of this i will of course try to update the plugin/gateway implementation asap if at all possible.
it may also be the case that at some point they do not even offer any API anymore , or even only some proprietary software of some sort (unlikely, but possible)
All i can say is that quite a few of the omnikassa implementations are in use and seeminigly working without any problems as i have not had anybody contacting me for months regarding any issues with it
hope that helps
-
AuthorPosts