You won't see any update notice in the program. This will be the final if no critical bugs will be noticed.

If you never updated please just wait for the final version since you will be able to use the update page instructions.

v.1.18 alpha

• Added replacements for websites.
• Added option in "WEBISTES" -> "Other settings" -> "Convert message to HTML". Might be useful when replacing whole post, but have new post in BBCode and website only supports HTML.
• Other small improvements and fixes.

Final already released: viewtopic.php?f=2&t=6289

Just encoutered an error message:


I found the cause quickly: it was faulty regex. In my case character 41+42 should have been "\n" but there was only "\".

It's really cool you inform the user even about the location of the regex fault but the error message itself should be more clearer about that probably faulty regex is the source and no "internal error" - an "internal error" might get you a bug report here, a hint to check regex will probably cause less support requests - just a hint from someone who ist happy with his new toy ;-)

Wurstmu

The error message does not really come from me, but from third party regex parser.

If it gets confusing and I will receive a lot of questions regarding that I might think something out to improve it.

Maybe it's worth noting it in the FAQ when you update it for release version though.

Wurstmu

If I am right the first thing the regex engine does, is replacing [LINKS] tags, right?

If so I encountered a strange thing; I have a case where a part of a link tag stays in the posting.

I worked around it like this:

- Replace links tag with custom tag "links" (no joke!)
- Erase those tags with replacements: (?i)\[\/?links\]\n
- Result is as expected, finally

Quite funny, seems to be really a bug, I have poked around in my replacements for half a day now - there is nothing that should cause this. I can post / PM further details if you want it.

This will be very hard to reproduce I guess, but I'll help as much as I can.

Wurstmu

Check PM.

Just for the record: my assumption links-tags are parsed before user regex were wrong, as freddy explained to me via PM. Conclusion: This may still be faulty regex on my side, will look further before giving details.

Wurstmu