A recent forum post was a good example of the way Kunena corrupts web addresses in the email notification.

The actual web address was www.joomlahackers.net/joomla-1.6-tutoria...es-in-joomla-16.html (joomla.org.au/forum/joomlaoz-tips-and-tr...s-in-joomla-1-6#3977). The emailed web address was www.joomlahackers.net/joomla-1.6-tutorials ot-able-to-order-modules-in-joomla-16.html - note space (2011-03-31_0649.png).

I expect that the email version of this post will also be corrupted!

As an experiment, here's the web address presented in another way.

Note: This is a variation on a previous post.

Mm yeah. Thx Pete. Did you track a solution?

No, I haven't yet looked for a solution - just wanted to register the problem first. Same with the upload problem.

Note: Read this on the webset - will be corrupted in the email.

This problem is in the purify() function in /components/com_kunena/lib/kunena.smile.class.php line 202.purify() gets rid of all sorts of special code before emailing. Line 202 must be supposed to get rid of line feeds (who knows why) but converts the text "/n" in the web address to a space " ". So, any web address that has an "n" following a space will be corrupted.

And so,is converted to Can anyone suggest what this line might be trying to do? My Regex doco doesn't know about the use of "#".

In the meantime, Dex, if there's a newer version of kunena.smile.class.php, it might be worth trying.

Note: Read this on the webset - will probably be corrupted in the email.

A similar problem was already reported at joomla.org.au/forum/bug-reports/kunena-n...ails-ampersand-error

This problem is also in the purify() function in /components/com_kunena/lib/kunena.smile.class.php. This time it's line 121.

I posted this problem in the Kunena forum (www.kunena.org/forum/168-k-16-support/90...ion-of-web-addresses).

In 3 days, no response to my post to the Kunena forum

Now, that's unimpressive!

2 weeks now and no response from Kunenaland.

Dex, should we go it alone and fix this problem?

I think this has been solved in K 1.6.4 (still not publicly available, sorry); please remind me in a few days after JAB11 has finished and I'll check this matter with the Kunena development team.

K 1.6.4 has been available for release since 7 May. Recommend that this site upgrade to K 1.6.4 ASAP and implement a range of suggestions I have made by email to Dex.

Tidying up bug reports tonight... Before posting other ones.

If this is solved now, can you amrk it as such Pete by editing your original post topic to insert [solved]

I'd totally forgotten about this one, Patrick. Rather poor support on the Kunena website!

This is a test link.

And in plain text as well - www.joomlahackers.net/joomla-1.6-tutoria...es-in-joomla-16.html

As I don't receive my own emails, can someone check that these emails have gone through OK?

I see that this site is using an outdated version of Kunena. I suggest that you follow up this problem on the Kunena forum after upgrading to K 1.6.5. You should also be aware that there are plans in hand to release K 1.7.0 within the next couple of days.

Pete,

Fixed your link in your post. It had an extra . at the end to break it.

Sozzled's now our inside man for www.kunena.org/forum issues, so at the moment we'll schedule in an update to 1.7 next week once it's released... not much point fixing bugs twice.

Still not 100% sure of what the issue is though. Is it something to do with URLs wrapping oddly in Kunena emails and thus breaking? This link should test the theory www.kpsystems.com.au/is-that-a-real-emai...-joomla-org-au-forum

If that is the case, then after we upgrade will check it again. It will be due to the text wrapping conversion routine cutting lines to 80 characters without looking at whether the line includes a URL.

PtrNrs wrote:


Sozzled - wearing your Kunena hat, there doesn't look to have been a response to Pete at all, so understandable that perhaps we should be working out whether this is actually fixed or not in 1.6.5 and 1.7.0

To be specific about this problem. When a web address contains forward slash + 'n' as it did in the web address I was testing, for the purposes of the email, Kunena interprets it as a new line and therefore corrupts the email address. As I think I noted in the Kunena post, this appears to be symptomatic of other problems.

For instance, when Nathan wrote in a recent post, "usability: a case study" it came out in the email as as "usability: a case study". So if you're reading this in the email form, you probably won't understand what I'm talking about

In response to two last posts, there hasn't been activity from the Kunena project on this matter simply because the question was not followed up on the Kunena forum. Each day we receive 50 or more questions and sometimes older issues can be overlooked. I, personally, can't comment on why this wasn't followed up (either by Pete or by the Kunena project) and I really can't offer any technical explanation for why things aren't working the way that they should. I simply want to make the point that I thought the problem had been fixed - and that may or may not be the case - but that it is more appropriate if it is dealt with as a Kunena support issue.

I should also add that I am responding to this question because I am subscribed to this topic and I received an email notification about it.

As Patrick is also aware, I won't be available to answer questions about Kunena for several weeks but I am quietly confident that, if the matter is raised again on the Kunena forum, someone will investigate the issues and response on the Kunena forum; at least, I hope so.

I hope that helps.

TESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTEST

Please let me know in this thread if the following link is faithfully transcribed in your email notification. This was a bug in previous versions of Kunena, reading "/n" in a web address correctly. We now have K1.7 and it should be fixed.

www.joomlahackers.net/joomla-1.6-tutorials/not-able-to-order-modules-in-joomla-16.htmlwww.joomlahackers.net/joomla-1.6-tutoria...es-in-joomla-16.html

Pete

TESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTESTTEST

Ah, nup. Still not working. As per your email discussing the notification email it's the /n not the /r that is the problem.

As the URL is not a joomla.org.au one, I don't think it's caused by sh404SEF.

www.joomla.org.au/not-a-real-page/should-give-a-404 will most likely show the same in the notification.

My attempt at color coding didn't work because of the URLs, but no, as Patrick said, it didn't work.