Skip to main content ↑ ↓
ElkArte 1.0 - release notes Started by emanuele · · Read 7894 times 0 Members and 1 Guest are viewing this topic. previous topic - next topic

ElkArte 1.0 - release notes

This is a summary of the major fixes and improvements since the previous release, if you are interested in the details, you can have a look at the repository, the detailed list of commits and changes is too long.

You can find the list of known issues at this address.

Major changes since ElkArte Release Candidate 2:
  • [func] It was impossible to install packages directly to EXTDIR (ref).
  • [func] Some scheduled tasks were not run (ref).
  • [func] Fixed hook sorting (ref).
  • [func] Fixed db_add_index in PostgreSQL (ref).
  • [func] Fixed pagination of some recent actions (ref).
  • [func] Consolidated shorten_text and truncate in to Util class in order to be fully "HTML-aware" (several commits)
  • [theme] The header is now split into multiple functions to facilitate addons changing it (ref, ref).
  • [func] Delayed loading of templates until $settings is available (ref).
  • [func] A new hook (ref).
  • [theme] Tweaked white space on message index (ref).
  • [func] More compact links in emails (ref).
  • [lang] Moved days of the week and months (both full and short versions) to single entries instead of arrays (ref).
  • [func] Mark multiple mentions as read (ref).
  • [func] Reduce the hassles of token errors (ref).
  • [theme] Fixed showing of signature errors in profile (ref).
  • [func] Removed some unnecessary cache engines (ref).
  • [func] Avoid using templates without body message in PbE (ref).
  • [theme] Fixed the News title (ref).
  • [theme] Moved some inline style to css (ref).
  • [func] Convert 4byte chars (i.e. iPhone emoji) to the corresponding HTML entity, only for MySQL (ref).
  • [func] Fixed php_to8bit to handle 4byte chars (ref).
  • [theme] Removed alt from i tags (ref).
  • [func] Debugging was not displaying style sheets with cache enabled (ref).
  • [func] Backported some fixes from SCEditor 1.4.6 (several commits).
  • [func] Like permissions is now board-based only (ref).
  • [func] Settings.{language}.php was not loaded when changing settings (ref).
  • [func] A session error while applying signature settings (ref).
  • [func] More strings escaped when sent to javascript (several commits).
  • [func] Added a new argument to the topicMessages function (ref).
  • [func] Fixed a bug pruning all the redirects (ref).
  • [func] Fixed a bug in conversion of HTML to BBCwith PHP < 5.3.6 (ref).
  • [theme] The "split" button was misplaced in the split topic template (ref).
  • [func] Bug in splitting topics (ref).
  • [func] db::insert function now accepts an hash for the data value (ref).
  • [theme] Clicking the "more" button in Display does not close the dropdown (ref).
  • [func] Basic detection for opcache (ref).
  • [func] separation of apc and apcu cache (ref).
  • [func] Fixed the javascript for toggling cache options (ref).
  • [theme] Missing drop zone in Be Social! (ref).
  • [theme] Some misalignments (several commits)
  • [func] Thumbnails were not showing properly in the recent activity tab in profile (ref).
  • [func] Hard-coded the "via" in mailing header (ref).
  • [theme] Some colors were wrongly positioned in index.css instead of the variant file (ref).
  • [func] loadLanguage was loading multiple times the languages other than English (ref).
  • [func] Avoid overriding of today and yesterday in profile (ref).
  • [theme] Removed duplicated id in the search form and fixed the results template to match all the others (ref).
  • Other minor fixes.

143 commits and a total of 96 files have been changed since ElkArte Release Candidate 2.
Last Edit: October 05, 2014, 08:35:24 am by emanuele
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 - release notes

Reply #1 –

Great update, moves Elkarte that much closer to stable release.

Re: [WIP] ElkArte 1.0 - release notes

Reply #2 –

Run, Elk, run..

Re: [WIP] ElkArte 1.0 - release notes

Reply #3 –

Are those theme changes very big? Would there be a good bit of work trying to port them from RC2?

Re: [WIP] ElkArte 1.0 - release notes

Reply #4 –

There are some changes around.
Some important ones to index.template.php and some to less modified files.

The attached is a diff between the RC2 and the current master (what should be 1.0 final unless of other issues), you can search for the files you have changed and see what are the differences.
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 - release notes

Reply #5 –

There are many changes as I can see. I will stop making themes until 1.0 version, so there's less work in long run :)

Re: [WIP] ElkArte 1.0 - release notes

Reply #6 –

That looks like the diff for all the template files (all templates, js, css) so its a lot more change than what is going to effect your efforts.  Of course we are at 1.0 at this point as well, so the changes are kind of done.

Attached are some side by side report files (htm) that show the changes to each file rc2<->current, should make it easy to add things that you may need.

Re: [WIP] ElkArte 1.0 - release notes

Reply #7 –

Yeah, some more than I wanted in fact.
index.template is my fault, I shouldn't have changed it... :-\
Bugs creator.
Features destroyer.
Template killer.

Re: [WIP] ElkArte 1.0 - release notes

Reply #8 –

It's not that bad I see :)

Re: [WIP] ElkArte 1.0 - release notes

Reply #9 –

I hope that my question is not too stupid:

Would it be better (easier) to install 1.0  - and then try to upload the "old" index.css and index_light.css from 1.0 RC 2 again?
 

Re: [WIP] ElkArte 1.0 - release notes

Reply #10 –

Quote from: emanuele – Yeah, some more than I wanted in fact.
index.template is my fault, I shouldn't have changed it... :-\
I like that change, it made a couple of things I did extra easy, like the custom search box.

Quote from: Ruth – I hope that my question is not too stupid:

Would it be better (easier) to install 1.0  - and then try to upload the "old" index.css and index_light.css from 1.0 RC 2 again?
You can certainly do that, and it will work fine.  The css updates fix some simple things and it should be a easy to import those back to any custom theme.