BUG: Hardcoded table prefix causes errors

Hey Jos,

Thank you for reporting this. You’re completely right – that shouldn’t have slipped past us, but it happens to the best of us I guess. ?? I’ve gone ahead and fixed this for our next release, which will be released in two weeks from now.

If you’d like a beta fix in the meanwhile, please let me know!

I can’t see if this has impact on the correct functioning of the website. Why would you wait 2 weeks, while this can very easily been released in a quick fix. So I hope you choose to release it soon in 4.7.5.1

And please don’t mark a topic as resolved, when it’s clearly not solved yet.

• This reply was modified 4 months ago by Jos Klever.

Hey @josklever,

We may issue a hotfix release for this, but that’s a decision I typically take in discussion with my colleagues and not something we do over the weekend, so TBD basically.

I completely agree with you, but there’s a thin balance because people tend to get upset if we issue too many updates in a short period of time as we already put out a new release every two weeks.

This specific issue may cause terms to be excluded from the sitemap, but obviously only if your table prefix is different from the default (not the case for the large majority of our users).

In any case, I already uploaded the fix to SVN so anyone who’d update the plugin (or reinstall it) would get the fix.

People can decide for themselves if they want to install a hotfix, but I think it’s not rare to have a custom table prefix.

For now I’ve reinstalled it on all the sites I maintain.

Hey @josklever,

We just released a hotfix release for this issue. I’ll mark this thread as resolved now, but if you have any other questions, please let me know.