macaroniduck

And how does this work with your pricing? If I have a table displaying 50 items with like buttons next to them, that leads to 100 buttons “per page” which is beyond your budget based on your pricing.

Thank you for the response. I want to be very sure it can do the following also however. Can you have 2 different kinds of Like buttons attached to the same piece of content?

Correct. That is what we need so will continue the search. Thank you.

To be clear, I do like PODS. I’m using it on a site in conjunction with PostsTablePro to present some basic tables of posts/information and it works great. Unfortunately my current project involves migrating a site from Drupal where some more complex queries/Views need to be recreated that greatly benefit from a GUI tool to ease the process. Will definitely be watching PODS for future developements/updates!

To save others who may find this post the 40 minutes of watching a video. PODS provides some code/shortcode ways of querying data, including through relationships. There are no GUI tools or help with styling, etc. And all of this will require that you write HTML/CSS to pull it all together and style it. (This is all assuming that video showed all the possible functionality of PODS).

Here’s the issue for me. MC User Sync has inexplicably stopped working on one of my web sites. The error messages are not helpful. Now I’m learning it is no longer supported and will someday be a paid premium. I feel like the rug has been pulled out from under me as I have no path for support of a plug-in I’ve been using until/unless the new premium update happens. And at that point, I have to trust that it will fix the problem. Not a good situation when I need something working right now.

@wfphil,I greatly appreciate you taking a moment to reply. I believe I must have seen similar recommendations in other thread somewhere as I have implemented all of these changes.

The issue is quite perplexing as I can’t reliably reproduce it every time an action is taken. In other words, the only time I’m seeing it triggered is when saving a post/page while in the Divi Back-end builder (haven’t observed it in the front end). In continued testing on a staging site the other day, it look me a full 15 minutes of editing and saving before the issue was triggered. It took a bit longer to trigger it a second time as I turned some plug-ins off. This makes it problematic to take the “turn off all plug-ins and enable them one by one” approach.

It’s starting to look like my particular set up just isn’t going to work well on SiteGround. Perhaps this issue only comes up as I’m approaching limits they’ve placed on the server (though I’m on a cloud server so those aren’t supposed to be an issue). Nothing against SiteGround as I’ve always had good experiences with them, but I may need to experiment with trying this site with a different host to see if I observe the same issue.

Thank you! That will definitely accomplish the first part. Doesn’t look like the second will be possible, however, even with nesting (at least not on a list that shows events from more than one category).

This is a restricted membership site so can’t point to pages, but it sounds like you’ve got it. I’d like for people to see the calendar when they click into the Start Date field (in Advanced Search), but would like for it to default to the first day of the event.

I’ll look into whether that’s possible through template modification. I’d also appreciate this being considered as a feature request as I imagine it would be useful to many.
Thank you!

Unfortunately, I’ve settled on making 5.0 work and won’t be able to try that Hristo.

FWIW, I tried multiple times to rapidly delete the plug-in after a restore and it never worked. The update would happen immediately every time. Before I could even delete the plug-in.

I asked SG about that Mark, and they said there was no way to modify the backup files. I have my own backups. And it might be possible for me to address things from that direction. I gave some thought to how much time/effort that might take only to not find the issue and decided that time/effort would be better spend just plunging ahead into upgrading things for 5.0.

I will say that I highly suspect the issue was caused by one of two plug-ins that another host (BlueHost) installed when I was hosted there (the site was later migrated to SG). Apparently, BlueHost had a habit of installing “must use” plug-ins. From what I’ve read online, it appears they did this without informing users. I certainly don’t recall ever receiving notice about it. Yet, there they are. And again, I have no way to restore and then remove them to test the theory because the update happens immediately after restore, even if I add the updater_disabled code into the config file prior to restoring the database.

So, at this point, I may be spending the weekend upgrading this site. In order for me to turn off any plug-ins and revert to my previous version, keeping it from upgrading again, I need to do a restore. I have twice now restored both the files and the database. Each time I do, the site IMMEDIATELY upgrades to 5.0. I have no time to place define( ‘WP_AUTO_UPDATE_CORE’, false ); into the config file, nor to remove any suspect plug-ins.

Since this is a shared server host, I can’t disconnect it from the Internet to avoid the immediate update (assuming that would work).

Anyone have any ideas on how to keep it from immediately updating before I resolve to losing my weekend to making things work with 5.0?

Does WP not have a log somewhere that indicates when events happen and how they are triggered?

perspectiveexploration.com I already have an open ticket with you. Everyone at SG has always been very helpful. This problem is particularly vexing though.

tgedge1, No Softalicious or anything of the sort I’ve been able to find. SiteGround has their own updating system that you can place your site under and that’s the only cPanel type thing I’m aware of that would affect this. Continuing to investigate.

Thank you, Marius.

I’m well aware of the classic editor. My site is using an old theme, and old plug-ins and is not ready for the update. I had planned on the extra time due to SiteGround saying they would not be forcing the update. This is a ridiculous time of the year for a major update like this to have been released.