Forum Replies Created
-
AuthorPosts
-
November 12, 2020 at 3:08 AM in reply to: ✅Alert on critical error on website after installation of Meta Box AIO #22812
EddyPiV
ParticipantHi Long, no problem. Its working fine at my end, so let's close it. Seems false alarm.
November 10, 2020 at 12:40 AM in reply to: ✅Alert on critical error on website after installation of Meta Box AIO #22767ParticipantUpdate: I don't know why, but the critical error no longer appears and the system acts normally.
Yet, I find it weared and a bit concerning receiving such alert.Perhaps for you to have a look if action is required?
ParticipantNo, what I need is the time in my own timezone (Amsterdam timezone). In the settings of the website it is configured like that, but when I use .date('d-m-Y H:i:s'), it adds the time according to UTC, which is 1 hour different from my timezone. I understood that the date function is meant for the local timezone. So I wonder why it adds UTC time, and how to add the local time instead.
Thanks for your help.
ParticipantHi, Giovani, works perfect, thanks so much!
Just 1 question: I have added the time, tried varies variations, but it keeps coming with UTC time iso the local time.
Checked my settings, set to local (Amsterdam) timezone.
Any idea how to get that correct as well?ParticipantThanks, that works great!
ParticipantHi, the first scenario. It is a sort of attendance registration.
The user logs in, and then does the checkin. He will be the author of the post, but I want his displayname as title of the post.Hope that makes it clear.
ParticipantYes, that's working now. Thanks!
ParticipantHi Long,
The screenprint you sent I recognized, but I installed yesterday the extension version 2.0.4 and the screen looks different, and... the support page doesn't respond.
https://share.getcloudapp.com/P8uyKp7xParticipantFound it. Resolved.
ParticipantYes, that was it. The format mistake I already figured out.
Thanks, let's close this thread.ParticipantThat indeed resolves the critical error.
And some new questions arise...
Question 1:
There are 2 posts found, 1 with date today, 1 with date 3 days ago.
Yet, the post.date for both (according to the view) are shown as today. Why is that???
Print of database: https://share.getcloudapp.com/X6uN152L
Result of the View: https://share.getcloudapp.com/L1uJA65q
The View-code: https://share.getcloudapp.com/xQuL2Og7Question 2:
At least 1 post should be displayed with its details, but there are no posts displayed.
Considering the post.date for both showing today, both should be displayed.
Why are no posts displayed?
Something with stored formats? How to formulate the condition correct?ParticipantHi,
I know, the devil is in the details... I should have added the mb. prefix...
But it doesn't resolve the critical error.Deleting the "if" construction avoids the critical error, so it is really in this statement.
ParticipantActually, I found out that what I wanted to do wouldn't work: I was trying to set the expiration date fields of the Post Expirator plugin, but there is more needed to get it to work, probably setting a cron job.
So my question is now a bit different.
I am now skipping the posts that are older than 24 hours.I included this if statement: {% if {{ post.date }} > strtotime('-1 day') %},
but WordPress didn't like it... critical error on the website.Here is the view: https://share.getcloudapp.com/RBuOpJkA
ParticipantHi,
To me is doesn't make sense to define multiple taxonomies for actually the same thing, with all having the same items.
Anyway, I tried your approach and it indeed showed the pagination link, but also in case it shouldn't.
For one type I had only 3 instances, these were shown, plus the Next link.
Pressing that next link told me that there were 14 posts, and the last 4 were shown. So it looks like it thought it had shown 10 occurrences on the previous page...Whatever, it introduced new questions, and I have the feeling that I take 2 steps back again, while I am so close.
My decision is to stay with 1 taxonomy and with your solution for the custom pages based on get-posts, with a larger number of posts to show, and forget the pagination.
This works, looks nice, and I expect it will be acceptable to the client.Thanks a lot for your patience and help.
Let's close this thread.ParticipantHi,
That's what I meant when I said that for me the coding is more difficult for Custom views than for the Archive views. In the archive views we have the {{ mb.get_the_posts_navigation() }} function, but that doesn't work for the custom view.
I have puzzled many hours to get this figured out for the custom view, but without success. All the time I get "critical error on my website" message.Isn't there any help to get this easier supported for custom view??
-
AuthorPosts