viper2k wrote: When will you release the new version of Kunena 3.1?

I'm sorry but this topic is about the release of K 3.0.5. I am sure that, when someone takes the time to write some details about when K 3.1 will be released, this will be done in a different place.

viper2k wrote: Hopefully [K 3.1] comes with a more modern design and some new features.

Yes (for those who use J! 3.x). For those who use J! 2.5, K 3.1 will look much the same as K 3.0 does now.

In response to your comments about professional ticketing systems and "more templates" (which do not really have a lot to do with the announcement about the release of K 3.0.5), we are considering a range of options in relation to "paid support" but we are not in a position to provide you with those kinds of details.

There are a range of services available to you today for support, for additional Kunena templates and for a wide range of things involving Kunena. Perhaps a good place to start your search for services and templates is to look at the advertisements that appear on this website. I am sure that you will be rewarded for your efforts.

As you know, there is no company behind Kunena. Everyone who contributes to Kunena is a hobbyist, enthusiast or professional web developer who gives their time freely to this project - volunteers every one of us. The forum is provided mainly as a self-help community-driven resource for users but there is no "formal" obligation of support, necessarily. We do our best. Our job, in moderating the forum is not necessarily to answer every question but, rather, to point people in the right direction where they can find the answers. It is unfortunate (perhaps) that in this case I do not have a specific answer to the question "when will K 3.1 be released".

If you are interested in being part of the project team that is building K 3.1, and you have software coding skills that will assist the project, you might like join the GitHub community.

When will you release the new version of Kunena? 3.1? Hopefully it comes with a more modern design and some new features . I would also pay for the version if you have:

- professional support with ticket system
- some more templates

Thanks

plenty of support up to date features very modern working platform
so take it for a test drive and get a feel of what you can and can not do

Anastasiya: Please start a new topic in our Installation and Upgrade category and read the installation guide in the Wiki.

The situation with downloading large files remains the same. If the attachment is too large, the message "COM_KUNENA_UPLOAD_ERROR_NOT_UPLOADED", but not "COM_KUNENA_UPLOAD_ERROR_SIZE".

Thanks sozzled, no problem at all, I know how much you and the rest of your team have on your plate! And apologies, I didn't mean to hijack this thread. Just thought it was the most appropriate place since it was directly related to this release and could have been helpful to others looking to patch security quickly...

Will go for option (a) that you suggest as soon as I have 20 minutes or so to spare Thanks!

I do not know if Qoppa will read this topic or if he will reply directly to you with the information that you are looking for. I have to admit that for this K 3.0.5 release I did not prepare the release notes because I have been very busy doing other things (and so, if the information is not as complete as you will find in other release notes where I was involved in writing them, please accept my apologies).

So you are right. The "abridged change log" for K 3.0.5 does not specifically state exactly which GitHub bug. Sorry about that. As I said, I haven't had the time lately to review what's in the Wiki. :blush:

This is really not the best topic to ask these kinds of questions. It may be better for you to go to GitHub where you can search for the information that you're looking for. If you can't find the information in GitHub, you have the following choices:

(a) upgrade to K 3.0.5 (in the normal, recommended manner) and reapply any customised changes that you specifically want (or need); or

(b) create a topic in the Custom work - not offering to pay or Miscellaneous, off-topic and general Joomla and wait for another member of this community, who has a common interest in your problem, to reply with the specific information you are looking for.

Please remember, as a courtesy to other users of this forum, to not hijack this topic further by continuing to ask about how to make out-of-the-ordinary changes to your customised installation, questions that do not apply to the majority of other members of the community. Thank you.

Thanks for your prompt reply Sozzled.

I'd already looked through release notes (no specific mention of where the XSS vulnerability was, other than BBCode), and through GitHub (where the latest commit has over 1400 changed files, mostly with version numbers, etc, so it was almost impossible for a GitHub newbie such as myself to find which bit was responsible for the security flaw).

I'd agree with you generally though, that if I make core hacks, on my own head be it, though in the case of urgent security alerts, which are now public due to the update, it would be really helpful for someone on the team to be able to confirm which two or three files absolutely need to be patched (and I assume it's a tiny independent change in this case, such as all the files in library/kunena/bbcode or somesuch maybe?).

If Qoppa or someone who was responsible for finding / fixing the flaw is reading this, would be great if they could just ping a quick line across letting me know if any other files are at risk or if that would do.

I don't think that in the case of small security updates, which by their nature are more urgent and important than feature releases, those who choose to embrace Kunena's flexibility and open source nature by hacking it a little bit, can not be supported, at least a little bit?

Anyway, didn't mean to start a long thread or debate over this, it was literally just a quick request for help in case a kind soul happened to have an answer to hand.

Keep up the great work Team K!

naimless wrote: Quick question - could you please confirm which files I need to patch for the BBCode XSS vulnerability?

As you probably know, these kinds of announcement topics are not the best places to ask "quick questions" like those. Details about what is fixed (and how) are usually contained in the release notes and the full source codes is availabled (for those who want to get it) on GitHub.

naimless wrote: Have some core modifications done to Kunena (I know, it's not a good idea to hack core files) ...

This is an example of why we do not recommend to people that they should modify the original source code. People modify source code and then they kind of "paint themselves into a corner" and they're unable to upgrade to new versions because their highly-customised software contains so many changes that it takes a significant time to reapply them when new versions are released. However, as we have always said here, Kunena is open-source and people are free to change it as much as they like but, if they change it, they cannot expect that we will be able to help them when they do. My advice is to read the release notes (in the Wiki) to see what changes have been applied to the new version and then to go to GitHub to find the actual source code that relates to those things.

Hi,

Great work on the new release and security fix.

Quick question - could you please confirm which files I need to patch for the BBCode XSS vulnerability?

Have some core modifications done to Kunena (I know, it's not a good idea to hack core files) and would be great if I could just copy those files across without having to patch the other core files again with my modifiations.

Thanks!

Looking forward to this, and 3.1! Noticed a typo in the release note, 2nd line above the "Other Details" header:

"For this reason it is advisable that you first test K 3.0.4 on a test site before you upgrade your live production site(s)."

Should be 3.0.5, I assume.

Good work to all the volunteers who keep the prject moving on the back end and to the mod team who keeps all of us "dumb users" functioning!

Hello,

everything works fine. Thanks a lot ...

Hopefully 3.1 is not so far away...

Greetings, Roland

Discussion on about WYSIWYG editing is a very big subject. It is a huge subject, in fact. We have many other topics relating to people's desire for a WYSIWYG editor for Kunena.

In terms of what currently exists for the immediate future: there are no plans at this time to include [what most people commonly refer to as] WYSIWYG (i.e. TinyMCE or some other plugin) editing features as part of the core component of Kunena.

There will be no new features added to K 3.0; any future releases of K 3.0 will be confined to bugfixes.

The feature set for K 3.1 has also been defined; WYSIWYG editing features are not part of the design specification for K 3.1.

I know this topic is coming up on two months old, but these comments:

I do think it is unfair and incorrect to say most forums have a WYSIWYG editor.

and

We really like hearing all your suggestions

leads me to add my comments.

We are in the process of migrating from an old forums software package that my community has been using for nearly 10 years. It is running on ASP 3.0 (a late-90s tecnology). When I told them we were migrating to something "new and fresh" and promised features only avaialble in "updated technology", they were excited. The lack of a wysiwyg editor has caused an uproar, and is outshadowing every "new" feature that this Joomla!/Kunena/CB solution provides. It's like trading in your 1975 Ford Pinto for a 2014 New Soemthingorother, but not getting a radio or power windows. For them, it's unfathomable to think that "current standards" and "no wysiwyg" can be used in the same sentence.

coder4life says, "incorrect to say most forums have a WYSIWYG editor".

This chart indicates that it's about a 2:1 ratio of popular forums using some sort of wysiwyg as compared to forums who do NOT use some sort of wysiwyg.
en.wikipedia.org/wiki/Comparison_of_Inte...um_software#Features

Anyway... please add my vote to the list of those requesting a wysiwyg editor for posting in the Kunena forums. Even if it's just a simple tinyMCE plugin, which (from my long ago dev days) seems to be the easiest way to go about it.

please add new IFRAME code in next version of Kunena! Because FLASH code, people not can see flash videos on mobile phones!!!

NEW CODE (no flash):
OLD CODE (flash video), now no one use it:

Thank you! Now I can understand the problems behind the WYSIWYG editor implementation in Kunena. You have to understand us, the "users" we are not devs, we just using the softwares. Before your post, I tought (and I think not only me) it is enough to put TinyMCE under the Kunena and done. Now I know it is a bit more difficult. :laugh:

Thank you again for your time what you spent to wite your post, and answer my question. I think we need more posts like your to understand what's behind this project.

Happy new year!

Hello positivnrg,

I think you are misinterpreting Sozzled post as being aggressive. I think he is trying to understand your reasoning and point of view by providing us with some examples.


As for WYSIWYG editors and the reason why we do not have one in Kunena is a much debated topic among our team. However there are facts about why we have yet to put resources into coming up with a complete solution that I will detail below.

In designing a WYSIWYG editor we have long investigated the principles of security (access, injection), format storage (bbcode vs html vs wiki vs markdown), performance (up to millions of posts), feature specific content (spoilers, hidden text, configuration report). Taking these parts into consideration we have a wide range of challenges not normally investigated in less complex forum solutions, especially those that are not directly integrating with an Open Source CMS.

We receive common questions about why WYSIWYG is not included. We had to ask ourselves several questions weighing different methods of reasoning to many of our members suggestions, recommendations, and perspective of reasoning.

Why not use Joomla editor system?

• We are not sure if the content, without some custom work and very close inspection of the Joomla codebase, if the submitted format and its contents are safe to submit, execute and store.
• The editors are usually only used by a specific set of people in your Joomla installation, and as such pose less of a security risk if something malicious were to occur. (Taking an example from Joomla fresh installations visitors do not have access to editor tools, only those [Authors, Editors, ect.] designated by ACL)
• Security issues that occur in features used by Kunena in Joomla (for example an undesired outcome of safety checks about what is being submitted) will make your Kunena installation vulnerable.
• Editors can be installed and uninstalled at the site administrator discretion, editors may not remain consistent during the lifespan of a website, as such can create inconsistency in the storage content.
• Multiple editors can be used that use different types of storage format as well as custom parsing and output display.
• Editors with different parsing methods requires us to take in consideration the possibility that multiple formats could be used per post, parsing occurs for those different formats creating performance issues with pages with hundreds of posts. (One editor can use BBCode, another could use HTML, and a third might use Wiki Syntax)
• Some features may remain absent in different editors.
• We need to handle a situation when an upgrade occurs and the format has to be modified, or changed to a new format.

Why not use a BBCode only solution?

• Does not address the ability to use Joomla functionality of multiple editors.
• Still requires us to implement all of Kunena's custom BBCode.
• Requires us to support a proper parsing scheme.
• Requires us to support across multiple browsers (this is a reason why most WYSIWYG editors still have not provided a 100% successful implementation, suffer from weird oddities, and require many hours of maintenance overhead).

I do think it is unfair and incorrect to say most forums have a WYSIWYG editor. Doing a quick search myself I see most free solutions have the same BBCode insert structure we have now. Sure there are exceptions, but to my knowledge few support a large complex WYSIWYG implementation to deal with many of the problems detailed above. I also see some provide their own solutions, but as a result disregard general reasoning about portability and customizations in regards to the wider context of how Joomla can be used. Most WYSIWYG implementations I find are part of commercial based forums that have to consider a specific set of security considerations, one storage format, and one area of performance considerations due to the one storage format.

This is not to say we do not want a WYSIWYG editor working with Kunena. On the contrary we see it as a valuable asset to making discussions move in a way people feel they should be expressed. It specifically improves having to imagine what the destination visual format is going to look like. As a designer at Kunena this is a high priority of mine that I have been investigating over the last several months. Specifically I have been looking into how we can improve the interactions using Kunena software.

Our team has discussed the various angles to the problems detailed above. We have some pretty good ideas in how to solve them, but like everything we do here we have to take careful consideration into the wider perspectives of Kunena software and priorities. We at Kunena are focused on having a solid communication platform using a forum based discussion structure.

We really like hearing all your suggestions, and we are working towards making Kunena the best it can be. We want to make sure we approach the issues behind WYSIWYG in a smart way, with the needed resources to maintain it.

Hmm I don't know why you think I was wrote about J! forum extensions. BUT when we talking about J! extensions just look arround! The Kunena is a J! exension. Of course it is the best extension when we talking about the forum type extensions of J!.

...

And, when we talking about the forums, (in this case I talking about the forum solutions J! based or not, it doesn't matter) I think 99% of them using WYSIWYG editors. So I think it is not a really "extra".

You think about Kunena as J! extension (and it is true) but for most of the "fans" it is THE FORUM SOLUTION!

Sorry if I too complicated in this post, Im too tired.

PS.: Why you are so aggressive / ironic? I just asked a question. Lot of your posts are negatives. :dry:

positivnrg wrote: Every forum, component etc works with WYSIWYG.

Thank you for the feedback. We are working on a WYSIWYG editor for future version of Kunena. I do not know when this WYSIWYG editor feature will be available but, as a guess, possibly as early as middle-to-late 2014.

As a matter of interest, can you provide us with the names of two forum extensions developed for J! 3.2 that use a WYSIWYG editor? Are these forum extensions commercial or non-commericial? I searched but I was not able to find any.

Hmm. WYSIWYG editing is a minimum requiments now... Every forum, component etc works with WYSIWYG. And you guys want to put in the buyable package? :dry:

Please delete all "Flash" embed-codes!

Now only Iframe embed-codes used in web!

NEW YOUTUBE CODE(no flash, only iframe):

<iframe width="560" height="315" src="//www.youtube.com/embed/asdasdasd123?rel=0" frameborder="0" allowfullscreen>

OLD YOUTUBE CODE (with flash):

<object width="560" height="315"><param name="movie" value="//www.youtube.com/v/abcdef123?version=3&amp;hl=ru_RU&amp;rel=0">

Improved site performance
Fixes the category sorting problems identified on J! 3.1 sites
Compatible with J! 3.2 It is ok to

Kunena 3.0.3 - WOW! thx!

In K3.0.1 there was a bug where unstranslated string showed up, but it shouldn't affect the updates in any way.

Here are a few things that need to be taken into account on automated updates:

1) We publish automated updates only 1-2 days after the release (except for security releases) to make sure that we get initial feedback before thousands of sites break.

2) Joomla uses caching on the update component, which means that users might not see the updates without sleeping overnight or purging update cache.

3) Updates from Kunena 2.0 backend are broken and there's nothing we can do about it without making another k2.0 release. In J! 2.5 use Joomla updater instead..

In Joomla 1.5 you're out of luck as Kunena 3.0 doesn't install into it because of we removed all the legacy code.

I believe there is a bug in Kunena 3.0.1 where the Joomla 3.1 Dashboard will not display the update icon and update message. Please try this and let us know any problems on these specific Joomla versions.

If on Joomla 3.1 go to Joomla Extension Manager, click Find Updates, see if 3.0.3 is there, check Kunena 3.0.3 and click Update.

OR

If on Joomla 2.5 there is an extra step. Go to Joomla Extension Manager, click Purge Cache, click Find Updates, see if 3.0.3 is there, check Kunena 3.0.3 and click Update.


Also a note to Jiminimonka post, the reason we suggest to clear the main Joomla Cache [not the Extension cache like I describe above] because Joomla tries to preserve specific pieces [over an interval of time] so the page/data can be sent faster without us having to reprocessing everything. There might be a bug were this page/data is not refreshed. This might be why the update icon and message is not appearing.

It could be to do with Joomlas extension cache, although this is a matter of debate (which we are having at the moment in moderators chat).

Just wondering why the fact that there is an update is not visible in the backend. In 3.0.1 the icon on control panel and Kunena component itself showed that update was available.

Hello,

update and everything else works great!

The new responsive design also very good and helpful.

Greetings, Roland

Nice! I try it immediately.

Not much chance of that. As Joomla moves ahead (and Kunena is keeping pace with Joomla), the minimum requirement is PHP 5.3 for Joomla. Because K 3.0 (which is currently the only version that the project team now supports) utilises some of the advanced features in PHP 5.3, it follows that you will need to move ahead anyway in order to stay in line with the way that things have developed.

If K 3.0 relied on PHP 5.2 then Kunena would lose its compatibility with Joomla and, because of that, Kunena would no longer remain the most popular extension that people download from the JED . That's just stating a simple fact.

As more and more people gravitate away from J! 2.5 into J! 3.x, the requirement is now to switch the dependency to the latest versions of PHP. If webhosting providers are reluctant or unwilling to upgrade their services to meet the needs of their customers, it also follows that people will search elsewhere for webhosting providers who are more responsive to their customers' needs.

To cut a long story short, K 3.0 (and, looking into the future) needs PHP 5.3.

Indeed - My bad and apologies.. My bad but meant that my host is running 5.2.14. Actually contacted them and they are reluctant to upgrade because of changes or removal of register_globals.. So any chance for 5.2.x compatibility?

The minimum technical requirement for K 3.0 is PHP 5.3.1 (although PHP 5.4.14 is recommended). If you are currently running PHP 5.3.x then you should not have a problem.

Any plans to roll back the requirement of PHP Version 5.4+? My host (and many??) are on 5.3.x and have no intention of updating any time soon. This renders me, and anyone like me 'stuck; at 2.x of Kunena.

Thank you
Had problems with birthdays. to wait the update.
be updated automatically from joomla?

Hello,

this is something i have in mind, but for now i'am focused on others things

Any plans to support Joomla core Captcha plugin, so we can get rid of reCaptcha?