[Eric Reynolds]

I just received word from Barry that you are aware of the issue and are working on a fix for a future release.

Thank you.

🙂 Eric

[Eric Reynolds]

I just received word from Barry that you are aware of the issue and are working on a fix for future release.

Thank you.

🙂 Eric

[Eric Reynolds]

The full console report is as follows:

JQMIGRATE: Migrate is installed, version 1.4.1
dependency.min.js?ver=4.7:1 Uncaught TypeError: c.dependencyVerified.className is not a function
    at HTMLInputElement.verify.dependency (dependency.min.js?ver=4.7:1)
    at HTMLDocument.dispatch (jquery.js?ver=1.12.4:3)
    at HTMLDocument.r.handle (jquery.js?ver=1.12.4:3)
    at Object.trigger (jquery.js?ver=1.12.4:3)
    at Object.a.event.trigger (jquery-migrate.min.js?ver=1.4.1:2)
    at HTMLInputElement.<anonymous> (jquery.js?ver=1.12.4:3)
    at Function.each (jquery.js?ver=1.12.4:2)
    at a.fn.init.each (jquery.js?ver=1.12.4:2)
    at a.fn.init.trigger (jquery.js?ver=1.12.4:3)
    at HTMLDocument.i.run (dependency.min.js?ver=4.7:1)
verify.dependency @ dependency.min.js?ver=4.7:1
dispatch @ jquery.js?ver=1.12.4:3
r.handle @ jquery.js?ver=1.12.4:3
trigger @ jquery.js?ver=1.12.4:3
a.event.trigger @ jquery-migrate.min.js?ver=1.4.1:2
(anonymous) @ jquery.js?ver=1.12.4:3
each @ jquery.js?ver=1.12.4:2
each @ jquery.js?ver=1.12.4:2
trigger @ jquery.js?ver=1.12.4:3
i.run @ dependency.min.js?ver=4.7:1
i @ jquery.js?ver=1.12.4:2
fireWith @ jquery.js?ver=1.12.4:2
ready @ jquery.js?ver=1.12.4:2
K @ jquery.js?ver=1.12.4:2
dependency.min.js?ver=4.7:1 Uncaught TypeError: c.dependencyVerified.className is not a function
    at HTMLInputElement.verify.dependency (dependency.min.js?ver=4.7:1)
    at HTMLDocument.dispatch (jquery.js?ver=1.12.4:3)
    at HTMLDocument.r.handle (jquery.js?ver=1.12.4:3)
    at Object.trigger (jquery.js?ver=1.12.4:3)
    at Object.a.event.trigger (jquery-migrate.min.js?ver=1.4.1:2)
    at HTMLInputElement.<anonymous> (jquery.js?ver=1.12.4:3)
    at Function.each (jquery.js?ver=1.12.4:2)
    at a.fn.init.each (jquery.js?ver=1.12.4:2)
    at a.fn.init.trigger (jquery.js?ver=1.12.4:3)
    at i.run (dependency.min.js?ver=4.7:1)

[Eric Reynolds]

I had the same error display upon submitting an event. I discovered that the issue was related to the tribe-events directory in my child theme directory. Removing the directory resolved the issue.

After the latest update, I suppose that some of the child theme directory files in tribe-events > community need to be replaced with new files from the updated plugin. Of course, any additions or revisions to these child theme files should be copied over.

I hope this helps.

Eric

[Eric Reynolds]

I had the same error display upon submitting an event. I discovered that the issue was related to the tribe-events directory in my child theme directory. Removing the directory resolved the issue.

After the latest update, I suppose that some of the child theme directory files in tribe-events > community need to be replaced with new files from the updated plugin. Of course, any additions or revisions to these child theme files should be copied over.

I hope this helps.

🙂 Eric

[Eric Reynolds]

Hi Andras. I’ve done everything you recommended. The issue doesn’t occur with Twenty Sixteen.

I am using Elegant Themes Extra theme (same as Divi with additional features).

I wonder if it’s an easy fix. 🙂

[Eric Reynolds]

Thank you Geoff. Problem resolved. 🙂 Eric

[Eric Reynolds]

Thanks Geoff, unfortunately, the CSS didn’t work. The “Show all categories (13)” link still displays I cleared the site and browser cache to no avail.

Any other recommendations?

🙂 Eric

[Eric Reynolds]

Thank you Hunter. I appreciate it. I have successfully revised everything that I need, but, for some reasons, changes to my child theme version of organizer-fields.php or organizer.php don’t display on the frontend.

For example, I do not want “Create New Organizer” to display on the community submissions form. I removed the selector via CSS, but I cannot get rid of the label. :p

• This reply was modified 10 years, 2 months ago by Eric Reynolds.

[Eric Reynolds]

Thanks for getting back to me Josh. I uninstalled all three Events Calendar plugins and reinstalled them. Now, everything is working fine. It’s a mystery to me but I am cool as long as things work.

Thanks for your help.

🙂 Eric

[Eric Reynolds]

I’m not sure that reinstalling all of the plugins will help as the code remains the same. You can always check the plugin versions via ftp. Go ahead and remove the existing directory for community events and replacing it. Let me know how that goes.

Coffee is good.

🙂 Eric

• This reply was modified 10 years, 4 months ago by Eric Reynolds.

[Eric Reynolds]

Hi Tom. Sorry that you are having issues. It may be that you’ll need to completely remove the community events plugin via ftp, and then upload the new folder. After you replaced the plugin folder, did your site acknowledge the community events plugin as version 4.0?

The only time I had a similar issue as yours is with my shared server. I mainly work on dedicated. However, I remember a situation when I had to remove any caching files before replacing the plugin. :p

🙂 Eric

• This reply was modified 10 years, 4 months ago by Eric Reynolds.

[Eric Reynolds]

This reply is private.

• This reply was modified 10 years, 4 months ago by Eric Reynolds.
• This reply was modified 10 years, 4 months ago by Eric Reynolds. Reason: grammar

[Eric Reynolds]

This reply is private.

[Eric Reynolds]

I downloaded the latest version of the community plugin (4.0) from my The Events Calendar account, and then I replaced the existing plugin folder via ftp. That was the only way that I could do it. Like you, I couldn’t get around the error.

When you replace a plugin via ftp, you do not have to activate the plugin because, according to the error, it was active when you updated the Events Calendar plugin.

🙂 Eric

• This reply was modified 10 years, 4 months ago by Eric Reynolds.

[Author]

Posts