(10-11-2010 12:13 PM)ZiNgA BuRgA Wrote: [ -> ]RateU pointed out that this plugin doesn't handle [attachment=] style tags properly.
Unfortunately, I don't see a good way of resolving this, considering how this plugin was designed, so I'll probably need to re-create it in a completely different way.
Sorry about that.
Scrap that, I figured out a bit of a dirty workaround for this.
Updated to v1.1 to fix the [attachment=...] parsing issue. The workaround slows the plugin down slightly, but it's still significantly faster than default MyBB behaviour (see updated benchmarks in first post).
Also, this plugin will now work on SQLite/PostgreSQL (as long as MyBB fully supports them).
Thank you Zinga, I have installed, seems ok with my attachments
Thanks for the update, Yumi
Downloading now, thank you.
It's Alive!!!
Thanks to RateU for discovering a small glitch in the plugin, with "$1" in posts being hidden.
This has been resolved in v1.11.
Note that you may have to clear the parser cache (ACP -> Tools -> Recount & Rebuild) if you are already experiencing this issue.
It seems that there's still a few problems with attachments inserted into posts via [attachment] code:
- the downloads count may not update
- there may be an issue with unapproved attachments and visibility of them depending on what is cached
I'm thinking that fixing these may require a bit of a redesign...
I have been using Tomm's usertagging plugin from MyNetwork, and it seems there is a conflict with the pre_parser plugin.
When I first submit the tag it works fine, but on page refresh, or returning to the page the tag has been changed from
@user to <-- @username -->
The plugin is here:
http://resources.xekko.co.uk/mynetwork/f...http://resources.xekko.co.uk/mynetwork/features/post-ta
I have reported this to Tomm. The forum I tested on has no special features, and when I deactivated the pre_parser plugin the tagging worked.
I think the design of the preparser ultimately will just conflict unfortunately. And I don't think there's really a nice solution.
I'll probably need to redesign this to fix that. Initially, I chose to design this at a parser level because it was different, quick to do, and potentially more flexible. But it seems that it'll have issues with various modifications >_>
Yes, I thought it would be a bugger to solve, it was more of a heads-up really. Thanks for the reply
signature links have problems. What can I do?