Forum Replies Created
-
AuthorPosts
-
EddyPiV
ParticipantPeter, my sites are hosted at WPMUDev, they have documentation about it here: https://wpmudev.com/docs/hosting/tools-features/#object-cache
Do you want me to check with them for a way that your development team can discuss this further with them?
As I don't think that me staying in the middle will be very practical.
Let me know.EddyPiV
ParticipantHi,
I got a response from the support unit of my hosting provider.
After further investigation, I found that the issue is with the Metabox plugin, which is not compatible with the Object Caching feature. This explains why it functions correctly on the staging site, where Object Caching is not active.
Please note that disabling Object Cache is not recommended, as it can significantly impact server performance. I suggest reaching out to the developers of the Metabox plugin to inform them of this issue, as it seems their plugin is not designed to be compatible with the server’s Object Caching.Can you pls have this checked and see if this can be resolved?
Thanks a lot, regards,
EddyAugust 23, 2025 at 5:53 PM in reply to: Posts created through Make don't get stored in custom table, still in postmeta #48811EddyPiV
ParticipantHi Peter,
I have created a showcase site and sent details through your contact link.
Good luck!EddyPiV
ParticipantI made a fresh copy in staging, and there it's working nicely.
I'm checking with the support team of my hosting provider. Hoepfully they can help solve it, or at least help understanding what / where to investigate. I may get back here.August 21, 2025 at 11:41 PM in reply to: Posts created through Make don't get stored in custom table, still in postmeta #48804EddyPiV
ParticipantHi Peter,
Yes, I mean the custom fields are not stored in the custom table, but still in the postmeta table.
I don't understand your suggestion. Whether the custom fields are stored in postmeta or custom table, isn't that a Metabox matter? Why should that affect Make? Make delivers the custom fields, yet they arrive in postmeta.
August 18, 2025 at 11:25 PM in reply to: ✅Getting query parameters from URL. It works and it doesn't #48758EddyPiV
ParticipantOK, I was hoping / expecting that there would be an easy way to get this.
Gemini helped me.
This is the function I added to my functions.php:/** * Gets a specific query string value from the URL. * * @param string $param_name The name of the query parameter to retrieve. * @return string|null The sanitized value or null if the parameter is not found. */ function get_query_param($param_name) { if (isset($_GET[$param_name])) { // Use sanitize_text_field to prevent security issues. return sanitize_text_field($_GET[$param_name]); } return null; }With mb.get_query_param('username') it's working nicely.
Perhaps others may benefit of this code, too.
EddyPiV
ParticipantThanks Peter, it's working now.
EddyPiV
ParticipantThanks Peter.
But then still, I get the error message 'Invalid request. Please try again' It's caused by the Redirect option. The URL I specify there is correct, pasting it to the url bar of the prowser shows the page correctly, but the redirect doesn't.
How to have the redirect working properly?
EddyPiV
ParticipantHi, I've taken another route.
When the user visits a specific page, I store the page URL in a custom field for that user, and I add there the query parameters to the URL, so that it's complete. (The page is only available to logged in users)
This works, the URL that's stored in the user profile is correct: when I copy it and paste it in the browser it shows the page correctly filled with the data from the query variables.That customer field is in the redirect, but it leads to an 'Invalid request. Please try again.' error.
So the URL is correct, but it looks like the redirect doesn't handle it properly.This is the command:
[mb_frontend_form id='paying-member-input-details' object_id='{{ post.ID }}' post_fields='' submit_button='Save' redirect='{{ user.tg_chat_redirect }}' ]Pls advise.
EddyPiV
ParticipantHi Peter,
Correct, there was a View with location Code - should have been Shortcode.
Solved, thanksAugust 12, 2024 at 1:35 PM in reply to: How to show relationships in same order as set in backend? #46135EddyPiV
ParticipantPeter, fyi:
I did a complete plugin conflict test with theme Twenty Four, and still the same.Looking forward to your advise.
August 10, 2024 at 7:16 PM in reply to: How to show relationships in same order as set in backend? #46131EddyPiV
ParticipantPeter, it didn't make a difference, so I've set up an admin account for you, and sent the login credentials as requested.
Thanks, good luck.
EddyPiV
ParticipantHi Peter,
Thanks, with your help I got it working.
EddyPiV
ParticipantHi Peter,
Thanks, with your help I got it working.
August 8, 2024 at 10:22 PM in reply to: How to show relationships in same order as set in backend? #46119EddyPiV
ParticipantPeter,
If I do that, they are shown in descending order of title, that's not the order in the backend.
That's why I tried orderby: none, hoping that it would result in the order of the backend, but it didn't work. That's exaclty why I started this thread.So any advise?
-
AuthorPosts