v3.0.7: expected end of February

hi people,

The idea is to release a new version in the weekend of 28 Febr.

a bit of information about the upcoming release

the version will contain minor changes. there have been post about Feature Requests and things for improvement, like post of Kralyk, Markus, but will postpone that for now. So if anyone want to dive into he/she is welcome to help out.

so what will it include:
- mainly some cleanup/codestyling of files, thx twitnic
- changed route.php
there was code that was commented out and it was causing problems so it's back in duty (thx Claude)
- fixed tooltip for attachments (#227 )
- fixed problem with plugin-finder ( #222 )
- fixed problem with date of module-wide ( #221 )
- fixed problem with group-view ( #234 )
- fixed problem with the display of categories (front) where it was showing the root category (thx Claude)
- added option to set default value for (un)registering in settings-view
- changed mailer text in case if creator
it was sending the wrong subject
- added language filtering
it will be possible to select/assign a language for events
- tweaked layout of editevent/editvenue
- changed cleanup image option in Settings view
there are now 2 options: cleanup or delete
- and some other things

will change a little bit more but it gives an idea.

to note: 3.0.7 is coming up this weekend as planned.

It's also time to look forward and can say that the intention for 3.0.8 will be (for me) to:
- change current attachment upload views
do like to add blueimp as that way things can be better checked (filesize to big, etc)
- change image upload (front)
registered people are getting a fileupload field, but why not giving them the option to select images from a dedicated folder like it was in EL (backend). so those views will be added back but only in the front and for registered people. Admins will still the com_media field and they can select an image from the images/ directory.
- modify the mailing plugin


will also try to make routing a bit better.

am going to:
- drop the multi-cat feature
- drop cat_events table
- alter a lot of query's/functions
- add catid to links
- use jcategory class (if possible)
we do have a category file within helpers and think that can be used to override things if needed
- add assets / rules

At the moment we're using multi-cat (multiple category's to 1 event) but as that's not fixed completely we're having problems with routing, access checking and it looks like it's not going to be fixed this year. So why not turn it around: switch to single-cat (1 event to 1 cat) till someone figures out how to deal with the multi-cat. do think it's better so am going to make some drastic changes.

Am thinking of adding it to the development or some other branch for now, so it's not going to be added to the master branch for the moment.

Maybe it is possible to implement the Update-Server-Mechanism (with releases in github). So the User can update from 3.0.7 to 3.0.8 to 3.0.9 to ...

Twitnic wrote: Maybe it is possible to implement the Update-Server-Mechanism (with releases in github). So the User can update from 3.0.7 to 3.0.8 to 3.0.9 to ...

can try it out..

Did see that the updateserver is pointing to this website, but the file doesn't exist. Besides that it wil need some more modification to be done.

can try it out..

tried it out but there is a problem.

We can't point directly to Github as Github is using https and that can lead to problems (fsock) so we have to point to a package on the site. As we're not having JEM3 for download here at the site that's causing another problem.

Ernst can upload the package and post it here at the site but can also point to another site temporary.

// am going to add updateserver tags into the packagefile