Abigailm

The theme authors have pushed out a theme update that corrects this problem. You can find the zip download by going to http://archive.cryout.eu/?dir=themes/mantra and downloading the file called mantra.3.2.0-comments-fix.zip

(This update is not yet in the WordPress theme repository because of other technical reasons, tied to WordPress requirements)

NOTE – I am not affiliated with the theme developers – I’m just reporting on what I have been informed by them in response to my communications.

I’d just add that I was able to get things working with a modification to the /includes/theme-comments.php – file. I think the reason it didn’t work for me before is because of database changes with the update process — and I had to roll back in order to restore the database.

If you want to make these changes, I would suggest using the comments.php file from the Kahuna theme as a model. Kahuna is another theme from Cryout Creations, but it has been updated much more recently — in June 2020 — and you can find its template here:
https://themes.svn.wordpress.org/kahuna/1.6.1.1/includes/comments.php

You can’t use that directly, because of the difference in function names — but the key difference is that it includes a “default :” specification within the switch statement, and that is the magic piece that assures that the script doesn’t come up empty.

Thanks. We are in different time zones, so by the time I saw your reply I also saw that you had pushed out an update to the plugin, so I simply ran the update. Everything seems to be working fine now.

Everything looks ok for me after the upgrade – thanks for asking.

Andy, it is working now and I might owe you something of an apology, as there might have been a caching problem when I tested version 6.4.2. My site is on Cloudflare so it turned out that I needed to clear all caches there as well as the cache used on the server. (Plus also a local caching issue – I had to do a hard refresh in my browser as well).

So I’m not quite sure at this point exactly what step fixed the problem — just that I need to once again remind myself to always clear all caches everywhere.

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

That seems to resolve the PHP error tied to the ticket plugin, but when I have the new version activated it blocks the loading of the venue map on the events view page. This is on all pages, not just those with tickets — so I think this is a separate problem.

I see a console error tied to javascript and I know from the changelogs that with the general upgrade that there were some changes to the way javascript is handled that might affect paths in some way. Here is what the console error looks like:

Uncaught ReferenceError: tribe is not defined
    at HTMLDocument.<anonymous> (legend-superpowers.js:139)
    at i (jquery.js:2)
    at Object.fireWith [as resolveWith] (jquery.js:2)
    at Function.ready (jquery.js:2)
    at HTMLDocument.J (jquery.js:2)

Good to know!

OK, I just figure out what is going on. I think it’s a glitch, not really a bug.

It has to do with Option settings, under “Default URL settings” – https://redirection.me/support/options/

In my sites I have the defaults set to Case insensitive and ignore trailing slash.

So on the 404s tab, it is simply not allowing me to override the defaults.

That’s not really a problem for me, as I want that default for all URL redirects. I can’t conceive of a situation where I wouldn’t want that– so as long as I am getting the behavior I want it doesn’t matter.

But the instructions on the options page seem to imply that the default can be overridden (“Applies to all redirections unless you configure them otherwise.”)

I think the expected behavior would be that when these defaults were selected, that would carry over to the 404s Redirect options to show those options already ticked — with the user having the option to untick them; or else simply to gray out those options if in fact the defaults cannot be overridden.

I realize that this is an amazingly useful plugin being distributed to more than a million users without charge, regularly maintained and updated — so I really don’t expect perfect.

At least for my purposes, it doesn’t matter now that I know that I am getting the behavior I want. Basically I was frustrated because I was trying very hard to select options that apparently I already had set as default behavior (but must have forgotten about setting).

This also explains why @sparker123 is seeing slightly different behavior.