Issue: Conflict with AME in non-wiki Forums

After reviewing the code for AME a bunch of times, I am still unsure what might cause this. Does this occur when the post is made via Quick Reply, the full editor, or both? Does this apply to both new threads and new replies, or just replies?

Let me check and get back with you. I know that it happens via quick reply, but I haven't tried the other ways.

I was getting the same problem and it was certainly happening with Quick Reply and the Full Editor replies. Not sure about new threads. My wiki is disabled at the moment for performance reasons so can't test it but I do plan on restoring it. This would be a big issue for me though.

I installed the newest public version of AME (2.0.2) and it seems to be functioning as intended (at least with this dev version of VaultWiki, and except when HTML is enabled by a mod - but that is a confirmed issue and they don't support HTML-enabled setups apparently).

I'm going to mark this as Not a Bug, at least for VaultWiki.

I can duplicate what is described in the first post here only with CES Parser Permissions active. This is an issue with having HTML-enabled on your forum via a mod (e.g. that allows HTML by usergroup). If you use something along these lines on your forum, you will have to come up with a workaround for the particular mod you're using.

Pegasus

I used to have this problem but recently upgraded Vaultwiki to the latest version. I noticed that Autolinks in the main forum are now not updating. The autolink tags are appearing around posts but they're not parsing (not sure if that's the right word).

I have disabled and uninstalled AME but that doesn't seem to have resolved the problem. Any ideas?

Thanks

Do you have a BB-Code Permissions mod installed?

No, the only Mods I have installed that affect BB Code were related to Video embedding but none of them affected BB Code permissions. And I've disabled AME.

Sometimes when I post something the Autolink will parse correctly but when I look at that thread later it's back to just showing the tags and it hasn't created the link anymore.

What version of VaultWiki do you have installed?
Also are the unparsed tags uppercase or lowercase (AUTOLINK or autolink)?

The unparsed tags are all uppercase.

File version is 2.1.1

Thanks for your help.

Just a bit more info on this Pegasus:

When you post something yourself then the Autolink looks fine to the poster themselves but to everyone else it just shows the AUTOLINK tags like it hasn't parsed. Then if you leave that thread and go back into the same thread it has no longer parsed and you just see the tags the same as everyone else.

I would recommend upgrading to the most recent version and clearing your forum's post cache. Let me know if that helps

Thanks for the excellent help again Pegasus.

I ran the query "TRUNCATE postparsed;" on the database and that seems to have done the trick.

Spoke too soon, logged off and went back on and it was all unparsed again. Had problems with clearing the post cache last night due to a duplicate threadid column error message but I'll try again later when I get home.

Right I'm on the lastest version and I've cleared the post cache and still have the same problems with the parsing. Any more ideas Pegasus?

After checking, you were not on the latest version (2.2.3 Patch Level 1). I have made the changes to your plugins that reflect 2.2.3's autolink changes (but you should still update ASAP).

It appears that perhaps you have not updated because the AdminCP was not alerting you to new product versions as it should have. I have created another report for this here: https://www.vaultwiki.org/issues/524/