Forum Replies Created
- AuthorPosts
-
It’s a bug in the preorder plugin I am in the middle of fixing (I assume you have that installed and page 2++ will be showing things just fine if you temporarily de-activate it)
(I believe this got broken at some point with an update of WPPizza rather than the preorder plugin , but that’s immaterial of course. Gets fixed asap and there’s a better way of doing that particular thing now anyway)
PS: you could use the “old” calculation of this by adding
define('WPPIZZA_DBP_DOWNGRADE', true);to your wp-config.php
but that might (probably will) get removed entirely at same point (it also does not account for any holidays set as those did not exist at the time)That said, fell free to make an argument and convince me why “days in advance” should be based on strict 24 hour interval and not actually like
1 == tomorrow (though that day may be closed of course, but irrelevant for this),
2 == day after tomorrow
etc,and I’m happy to look at this again
actually, seems to work just fine (on your test site anyway)
you are still open for today (at 17:35) so one day in advance, you can order for tomorrow (its a “day” in advane, i.e it being the next working day, not 24 hours from now. ) .now being 18:10 (you test site closes at 18:00 today) you will not be able to order for tomorrow. as intended
>Can you have another look into this please?
sure.
worked here fine, but I’ll copy your opening times and see if i can reproduce it (it’s a somewhat complicated beast as it clearly relies on whatever the current time / date is …that’s my excuse anyway )I belive 3.10.1 fixes this now (also addresses the 3-letter month date format settings issue for some languages in some months)
Obviously, if you have issues, let me know
ok, gotcha.
I’ll dig around a bithmm, trying things here with your copy, it works just as I expect so I must be missing something….
e.g. on your test site, currently being Sunday morning 3rd March when you are closed until 8 , I cannot order anything until Wednesday (6th March – as of course you are closed Mon and Tue)…
So what do I need to do to see what you are describing (and please be specific as to what outcome you would be expecting when doing things) ?
This reply has been marked as private.ok, at least its not language related (one less thing to worry about)
can i see your (non-working) preorder settings , together with a screenshot of your openingtimes plaese.
Could you also check – temporarily of course – if this issue still exists if your site language is set to englishthanks
>In the subdirectories of my clients, there is no file named “wppizza-customisation.php” at all.
evidentally there is though, otherwise the error:
“Undefined constant “ingrinfo” in /……../wp-content/plugins/wppizza-customisation/wppizza-customisation.php:16”
would not ever be thrown…. ?!?for completeness sake: as it stands, this problem will also occur if setting the date format to “Feb 26 2024” (i.e any 3 letter month format), always depending on overall language set
as a summary here (in case someone experiences the same or similar issue and comes across this thread)
– simply changing the date format in the preorder plugin (ignore WP settings etc) fixes things it appears
As mentioned above, I’ll see if this is fixable.
This may actually involve removing the “26 Feb 2024” format option altogether ….yet to be determined …
In any event, it will be addressed in the next update of the plugin one way or another
@johanfmp
Again , thanks for doing the donkey work here to narrow this down , much appreciated and very helpfulps> I noticed a file named “wppizza-customisation,”
got nothing to do with me as such (though probably based on this post here regarding portability -> https://docs.wp-pizza.com/developers/?section=filters-actions-functions)let’s start with the easy pickings first (may or may not be the issue of course)
from your debug:PHP Fatal error: Uncaught Error: Undefined constant “ingrinfo” in /……../wp-content/plugins/wppizza-customisation/wppizza-customisation.php:16
so you are using a constant that does not exist.
since php 8.2 (or perhaps even 8) this will cause fatal errors – i.e your site just dies – so you need to fix that to start off with (I do not think there ever was a constant called ‘ingrinfo’ anyway unless you defined it yourself ?!)ok. noted (thanks for jumping through the hoops to narrow things down and providing a workaround fix though)
Still a bit strange to be honest, so I’ll dig around a bit to find out what’s going on (and of course fix it if it’s doable)>Olly, it seems that the preoder (picker) has a problem with the dutch language
interesting and quite possible (may be dependent on date format settings)
i’ll play around with it here to see what is going on (I guess you have your – at least temporary – workaround )This reply has been marked as private.This reply has been marked as private.your debug is still saying
…session_start(): Session cannot be started after headers have already been sent…. - AuthorPosts