I don't have that Sources/Subs-Aeva.php on the version I installed. lol

Well, I have no idea what version of Aeva you're using so no idea what to be looking for, since there are three principle versions, Aeva Lite, Aeva Media 1.x and Aeva Media 2.x, of which only the last one is really receiving support (paid, though) and the other two only get support here if Nao or I can be bothered, which isn't all that often, really.

The fact my fix didn't work wasn't useless, either, it just clarified where exactly the issue is (since there are times this can happen in raw SMF too!)

The reason you can't create a new topic here is that there isn't free support here for Aeva, basically.


Oh, and that's not an Aeva bug you refer to, you cannot put a [url] tag inside an [img] one, plain and simple. The parser should be preventing it from happening. As you would find if you tried it on that forum, i.e. one without Aeva.

In theory it should never have parsed properly, but as of the changes in 2.0 RC3 and 1.1.11 (note: not even the latest versions), it should have been doubly disabled for security reasons to avoid malformed URL and XSS vulnerabilities.

You can't put tags inside tags, it's invalid HTML so it doesn't work. Better question is why it *ever* worked before.


Try it on simplemachines.org. They don't have Aeva. Funny though, it won't work there either. I wonder why... is it because it's an SMF issue with your messed up code perhaps?

Even the SMF team are telling you it's not an Aeva bug!


Since I'm feeling nice, here's a thought. I doubt the SMF folks would either know about this or bother to investigate.

Subs.php
$no_autolink_tags = array(
'url',
'iurl',
'ftp',
'email',
);
$no_autolink_tags = array(
'url',
'iurl',
'ftp',
'email',
'img',
);

Well, I doubt you'll get support on the SMF board, seeing how Nao is post banned, and the only reason I posted today was to re-assert the rights to my work on something.

I'd say 95% will be the same.

I don't know about that... depends how far we actually go with the changes I have mentioned elsewhere I'd like to do. If they all get implemented... it's a much bigger change than 5%.

I'm not asking you to switch to my fork.
Did I ever ask anyone to do that?
Why would I ask anyone to do that?

I'm making this fork because it was killing me not to be able to improve SMF just because it's managed by a bunch of morons. So, I'm putting my heart into it. Whether people use it or not doesn't matter. "If it doesn't work, use SMF." I don't even need to keep it compatible. And it won't be.

And here was me thinking I'd already covered this off anyway with hartiberlin, that we will not be guilt-tripped, no matter how innocuously, or intentionally, into making something that doesn't fit with what we want to make, it just so happens that what we want to make is what a number of other people want.


Breaking away from SMF, and breaking any chance of SMF compatibility on our side in the code were the two (first) best things we ever did.

Good to know you got it fixed.

I would have been able to help you figure that one out had Ad Seller Pro's author not acted the way he did.