Jason

Because that’s what’s required to replicate this theme. It’s not my theme it’s the theme I get forced to implement.

I did eventually get it mostly functional in the end but I still hate it and wish there was an easier, more logical way to do simple things like injecting HTML or added attributes within the initial wp_nav_menu function.

If wp_nav_menu had just a few more features it would completely solve this issue. Adding attributes to generated elements for instance or the ability to add HTML content before/after second or third level menus that’s different than the blanket before/after that is triggered regardless of the level.

It’s like wp_nav_menu is so close to being awesome but then fails at the last yard line.

Hi James, thanks for the response. Disconnecting and reconnecting my account did work. This is going to be rather tedious to do across all of my sites. Is there any word on when Multisite support is coming to Sitekit?

@juliarosia @sterndata Yes Julia & Steve, the Classic Widget plugin does indeed restore normal operation.

According to the plugin post it’ll be supported up until 2022 (which we’re in), is this issue going to be fixed going forward or will I need to eventually completely rewrite my widget areas using the new interface?

Sure, here’s the page that I’m talking about.
https://www.taftcollege.edu/human-resources/in-service-calendar/

You’ll see the inservice events listed in a table, under that table is a hidden version of the table /w the attachments column removed.
Before the the most recent-ish update, the plugin seemed to ignore the display:none; rule.

There’s probably a better way to do this and I am open to refactoring the page.

EDIT: Actually that did answer my question, I just added display:block; to the print-view css which I completely forgot was a thing and it’s back to it’s old functionality. I’m gonna mark this as solved, thanks!

• This reply was modified 2 years, 11 months ago by Jason.
• This reply was modified 2 years, 11 months ago by Jason.
• This reply was modified 2 years, 11 months ago by Jason.

Excellent! Thank you, this has saved me a LOT of time. I was using RSS feeds to pull a single custom post type from each site. The page took ages to load as it cached every item.
This is 1000X faster!

Hi Ben, I gave the jquery migrate helper plugin a go, and it solved some other issues we’ve had with updating the site to 5.5 but it did not solve this particular issue. The plugin is notifying me of several depreciations but not on the donations form page.

The only error I’m getting is that one above. And it’s only for the total area, the actual box where you can type in your donation number actually updates fine when you press a button.

Uncaught TypeError: can't access property "trim", t is undefined
    unFormatCurrency https://www.taftcollege.edu/foundation/wp-content/plugins/give/assets/dist/js/give.js?ver=2.9.5:15
    autoSetMultiLevel https://www.taftcollege.edu/foundation/wp-content/plugins/give/assets/dist/js/give.js?ver=2.9.5:15
    497 https://www.taftcollege.edu/foundation/wp-content/plugins/give/assets/dist/js/give.js?ver=2.9.5:35
    jQuery 2
        dispatch
        handle
give.js:15:49799

is the only error in the console and jquery migrate helper detects no issues on the page itself.

• This reply was modified 3 years, 10 months ago by Jason.

Update: I realized that our widget context actually isn’t a part of this plugin. I’ll have to get at it another way.

I guess a wishlist, other than to have this plugin actively updated would be to add multi-site awareness to both the widget and shortcode nativity.

I am also currently experiencing this issue on my Multisite. Attempting to replace a CSV file. I’ve added the CSV extension to the acceptable list of uploadable files, and am able to upload a new csv just fine. But attempting to replace the CSV with the latest version of this plugin, produces this error.

This is unfortunate considering gravity wiz’s alternative is $260.

I appreciate your work though, the plugin still works pretty well for me. I just hope a radical update on Gravity Forms part doesn’t do it in.

This plugin has been depreciated by the author in favor of gravitywiz’s Gravity Forms Nested Forms plugin. Which is very unfortunate considering the damn thing is $260 :/

At $260 Gravitywiz’s stupid plugin would be the single most expensive plugin on my network.

Hopefully someone takes over this project, license willing.

So I feel stupid, after a lot of work I took a closer look at the “comments“, turns out they were trackbacks, which were enabled for the posts. WordPress treats them the same which made me go into “omg I’ve been hacked” mode.

I guess it’s a good thing to run a regular scan of every single file on your webserver and check them against their online repositories though right?

The user, turns out, wasn’t compromised which made me do a closer look at the comments. She was just on vacation and changed her password from a very remote IP.

• This reply was modified 6 years, 6 months ago by Jason.

Yeah it looks like it might have been a compromised user of mine. I’m working through your list right now. Today’s going to be fun, thanks for the help!

Jason (@zushiba) – This sounds like a different issue to the ones above. You seem to have working lists, but events ‘disappear’ from the front-end. If you downgrade to 5.7.3 they just reappear again? Ideally I could have used a link to the site in question.

For both Jason and Christiaan, have you tried deactivating other plugins and/or temporarily switching to a default WP theme like 2017?

Not quite, that was an issue and it appeared to be fixed by downgrading to 5.7.3. Then the issue reappeared seemingly randomly.

The events generally (Not always) appear on the front end via the shortcode but cannot be clicked on as they produce a 404 error. And they disappear from the backend. That is, they cannot be seen, edited or deleted from the blog that created them.

Additionally, other sites on the network will count those lost events, even though they were never involved in creating them. So some sites will list that there is 1 or 2 active events and 4 or 5 overall events, when clicking on events in the Dashboard they aren’t listed.

I have a staging area, that is a direct copy of my life website. I have deactivated all other plugins on that site but I cannot reliably reproduce the issue on live let alone on my dev site. It’s very hard to track down what exactly causes the events to disappear.

I will create a post on your site as directed but I felt I should also keep this thread updated.

• This reply was modified 7 years ago by Jason.
• This reply was modified 7 years ago by Jason.

Thank you for responding Marcus, I’ll provide any and all information I can to help track down this issue.

What are you guys using to display future and past events? Shortcode, something else?

I also notice @zushiba you’ve mentioned the use of Site ID. Are you using MultiSite?

It’d be helpful to understand how you’re generating those events so we can try and replicate.

Do however double check you’re in 5.8.1.1, as this fixes a few issues for any dev/updates since 5.7.3.

For example, on our demo page, we’re running 5.8.1.1 and event listings seem to be working fine. https://demo.wp-events-plugin.com/

We’re using the shortcode to display the up-coming events on the main site, we’re using global tables mode and sharing down events to the main blog. In this case, the events do show using the shortcode, but the link takes us to a 404 error. New events (before they disappear) don’t do this, but when they do disappear they’re suddenly unavailable via the link.

The site affected is also showing that the events exist via the event count, but they do not appear in the event list anywhere.

And yes we are using Multisite.

I’ve updated to 5.8.1.1, it’s not detecting any orphaned events.

Here is a Pastebin export of 2 events that exist in the table, but do not show up on the site that created them. https://pastebin.com/U8Wv3vuJ

They do appear on the front end blog, utilizing the shortcode, but their links go to a 404 error. We are using WP Super Cache, but I’ve deleted the cache and they still appear.

• This reply was modified 7 years ago by Jason.
• This reply was modified 7 years ago by Jason.

Did this repair database option ever materialize? Because I’m still getting this same error and I still don’t see an option in the latest version to repair the database.