Forum Replies Created
-
AuthorPosts
-
>I’m just contributing my experience as business owner.
that’s fair enough , and I’m glad you did,
I just happen to disagree that forcing registration makes any difference whatsoever in validating whether or not people exist and just add the possibly to annoy potential customers
Hi
you are of course totally entitled to your opinion.
I am not going to argue with you in detail here as everything I think about this I believe I have already said in the topic you mentioned.
Allow me to reply to a couple of things though.
>I can not verify whether any order is a prank or someone has actually ordered an item.
i can’t see how registration helps there.>All of this can be easily evaded by users taking a minute to register
that’s the point. many/some probably won’t and take their business elsewhere to begin with>But if they have to call an IT specialist to integrate registration…
you don’t. as i said, use some other plugin. something like this springs to mind for example (though not tested), but there are probably many others
https://wordpress.org/plugins/pagerestrict/Hi
thanks for pointing that out
I’m surprised no-one mentioned that before actually.
Will be fixed in the next updateThis reply has been marked as private.a) never mind files/dbdump etc, you have duplicator installed so i just get the files i need that way (instead of explaining to you what this means)
b)re previous version – send me an email to dev[at]wp-pizza.com and i’ll send you the previous version in return.
HOWEVER, the previous version has EXACTLY the issue you are describing so i question the wisdom of using it.
Having said that, if it works for you – even only temporarily – while we get to the bottom of it, I’m more than happy toit isn’t really a matter of “knowing how to use the system” .
the question is , why does the customer data not get passed on / stored – and even more bizarrly – why does this only happen occasionally (somewhat thinking out loud here)
again: logfiles please !
also – if possible – a database dump of the wppizza_order table …something strange is going on … and i am beginning to suspect it’s got nothing to do with stripe at all…
we are talking across each other….:)
anyway
>look at my order history you will see two examples
but i also see the one in between that HAS the info !in other words:
i know that in version 1.3 there was a possibility for a customer to submit an order without entering his personal info (whether that would have been a wise idea is a different matter)as of v 1.3.1 a customer cannot do that anymore (i have verified this with other installations/ people)
if you downgrade you will open yourself up to this issue again….(and perhaps others if you downgrade further)
again though: as you have logging enabled form what i can tell, maybe sending me those *might* shine some light on it .
thing is this – from what i can see – it’s not that customer details did not get passed on (as you DO have orders with that info in it between the ones where yo dont)
issue is, that some customers – apparently – did not actually put in their info (personally i blame them for that omission, but there should of course have been a sanity check – as there is now in v 1.3.1!
a) you can use whatever version of the gateway you want (with the caveats of course)
b) I know the older version had an issue it would send an order through if customer didn’t put in required fields
huh ? that IS the issue you are having . am i missing something ?
the problem (and only difference) with 1.3 as opposed to 1.3.1 is that 1.3.1 does NOT allow you anymore to NOT enter required info whereas 1.3 omitted to do that sanity check
hmm,
i really cannot see how (not with version 1.3.1 anyway)
i don’t think this will give m any ideas/clues , but no harm having a look:
maybe you can zip up all log files in the logs directory of the stripe gateway and send them to me ( dev[at]wp-pizza.com )PS: it’ all back to what it was (i.e all i had changed was re-enable stripe to check some things and now i disabled it again)
ok, i’ll have a quick test.
i will enable a couple of things (leave things alone for a moment) and get back to you in the next 1/2 hour
with 1.3 that might have made sense (up to a point , discussion of which/why is irrelevant here for the moment) -with 1.3.1, i cannot see how.
could you turn it on again and i’ll check some things – or – if you prefer – tomorrow when you are closed (i can just open the shop in your admin for 5 minutes to be able to add something to the cart and mess around on the order page to check things or something to that effect)
> this is a must before allowing them to ….
i think you are slightly misunderstanding how this works.
in short, yes, you can do that, but you (the customer) does not make the selection before choosing half/half etc
the way to do that is as follows:
create/add “ingredients” -> thin, deep pan, crust, cheesecreate a custom group as appropriate and set these 4 “ingredients” there
group type -> one and one only ….(radio)…etc
and set
“Ingredients can only be applied to whole menu item even if half and/or quarters are enabled (has no effect when only whole is enabled)”outcome: have a look here
https://support.wp-pizza.com/twentytwelve/ -> “pizza half and half”>re flyout window:
sorry, that’s nothing i can advise you withdid you have that issue *after* updating to 1.3.1 (stripe) or before (i.e with 1.3) ?
24 May, 2015 at 1:40 am in reply to: Orders with invalid email addresses set to FAILED status #10123> based on my experiences with a very old version…
i’ll let you off then :)
>the option to show failed orders with reasons would be a great new feature
i only somewhat agree here. having said that, it should not be too much of a problem to add this.
will probably do this in the next version. however that’s still a bit away ( a couple of weeks minimum and there might be some interim version(s) ) as i am in the middle of adding a drag/drop template builder for emails and print order history rather than having to mess around with filters/templates. it’s kind of a big job , so cannot really give you an exact ETA.>I’m sure some businesses would find it useful, particularly during installation.
useful perhaps (up to an extend), but – to be honest – if the business does not know how to make sure their server sends emails, maybe they should get some qualified help in the first place.
…anyway, that’s a conversation for a different dayyou are mixing options 1 and 2
please read here
https://support.wp-pizza.com/topic/things-to-do-on-first-install/23 May, 2015 at 6:27 pm in reply to: Orders with invalid email addresses set to FAILED status #10113ignoring for a second here the obvious necessity to make sure that your email setup is correct:
a) > they claimed they saw no error messages
always an outside possibility of course , but i don’t think very likely (unless you are running a very old version of the plugin)..that’s just by the by …(though one of the next versions will have that writing highlighted a bit better)b)>I always make this little change…
surely, this is the wrong approach.
forcing a db entry to be completed as opposed to failed (when it did fail) is NOT what you should be doing.
what you *should* be doing, is DISPLAY any failed transaction so you know that and why they failed.
what you *are* doing is telling the db that everything is fine, when it was notin any event, i can probably add an option in the backend somewhere – either in the order history itself or under wppizza->settings->miscellaneous – to also display failed transactions (with the info why they have failed)
23 May, 2015 at 11:17 am in reply to: Orders with invalid email addresses set to FAILED status #10111this is not how the mail function works
simply speaking: it doesn’t care if an address does not exists. or if your settings are incorrect .
all it cares about is that there is no *fundamental* syntax error.whether an smpt sever or email address actually exists and whether the settings for it are correct it doesn’t know anything about
furthermore, of the 3 mail options you have in the plugin (mail, wp_mail, phpmailer) only the last one would let you set smtp settings (unless you are using a 3rd party plugin to override things, but that’s a different story altogether)
on a more practical level:
if that particular part of code you are referring to returns “FAILED”, the customer on the frontend would end up with a big error message along the lines of“Apologies. There was an error receiving your order. Please try again.”
so it does not really make sense to display this order anywhere as the customer will not expect (unless he can’t read) this order to be received/fulfilled, so the restaurant should not process the order anyway.
as mentioned, this will only ever happen if your mail function has been disabled for example or there’s something fundamentally wrong elsewhere
forgive me, but what you are requesting does not make much sense to me, but feel free to expand if i missed something
-
AuthorPosts