Okay, it is about time to have 1.1 up and running live here for some more deep testing before the release of the beta.
The general usage has been tested a tiny bit, so the basics should work.
I tested the upgrade script and it seems to work (TBH I didn't check every single detail, but in general I fixed anything I found broken).
So, considering that about 80% of the process looks good, it is "safe" to assume we can break the site and try the upgrade.
The full upgrade will require a little downtime. In the best case about 10 minutes, in the worst not more than a couple of hours (trying a couple of times, and in the extreme case reverting back to 1.0).
In order to maximize the mess, I will do the upgrade Saturday afternoon, around 2 pm CEST (UTC +2) unless I have unforeseen problems (I have just been informed I may be AFK, but it's not sure). If this opportunity slips, it will be "as soon as I have two hours", so likely Saturday at about 9 pm or Sunday 2 pm (always CEST, UTC +2).
A couple of warnings/reminders:
1) it's a dev version, it is expected to be broken,
2) it's a dev version, the db schema may still change,
3) it's a dev version, upgrades from other dev versions are not supported.
The first has another implication: during this testing phase there may be data loss even on this site. The worst case, as usual, is the reverting back to 1.0.x with a database backup taken just before the upgrade.
Well, fingers crossed! 8)
Footer says 1.0.6, so you are already missing 1.0.7...? Perhaps I missed some thread about it myself, idk.
Test
At least something works...
@Skull Knight let me see if I can bother people.
@emanuele there is something broken?
@Skull Knight apparently no, it works well... mostly.
Except you have to actually enable the notifications... try again?
Ouch! Dumb me!
Sorry
@Skull Knight I did it without thinking...
Yep, now it's slightly better!
Now it's time to fix the bugs!!
YAY!
Looks like it is somehow working.
Everybody!!Please note that to get the notifications (former "mentions") you have to go to:
profile
modify profile
* notifications
the direct link is:
http://www.elkarte.net/community/index.php?action=profile;area=notification
and set your preferences to: "notify when you are @mentioned", "Notify when one of your messages is liked" and "Notify when someone adds you as buddy", then save.
Something is indeed broken, if you find bugs
do not report them here, but have a look if someone else already reported it in the
Bug Reports (http://www.elkarte.net/community/index.php?board=2.0), and if not feel free to open a new topic.
Guys, we have 1.1 installed, have fun!
And let's fix the version, otherwise someone will moan it's not the correct one. :P
Why is the image attached as inline unreadable ? It is more of " thumbnail size ".
Would be nice to use a " loading " GIF than current " loading..." in text.
Which part of "do not use this topic to report bugs" slipped through? :P ;)
The sleepy part :P
/me slaps
@meetdilip to wake him up! :P
I enabled both desktop notifications and the little bubble showing the number of unread notifications in the favicon.
It may be slightly annoying at the beginning... well, it's testing of new features.
I got an alert asking whether or not to show notifications.
where to look elkarte 1.1 new features list?
It was asked a couple of times, but I don't remember if anyone managed to put a list together...
Off the top of my head I can think of:
in-line attachments,
"lightbox-like" zoom for attached images (Spuds, does it work for bbc images as well?)
more granular options for notifications (what and how to receive them)
use of SVG images instead of fontawesome
desktop notifications + the annoying number in the favicon xD
two-factor authentication
* possibility to change the home to other actions like recent posts or stats, etc. (actually still buggy)
This for the "user-facing" aspects, under the hood there has been another huge chunk of improvements on modularization and modernization of the code! :D
Can you pinpoint me please where I can find the 1.1 language files? I would prepare the translation...
The're currently not available.. I'll update the transifex account for 1.1 soon, however some strings will probably change in the next few days,, at least the 2fa strings require some fixes..
Okay, we better wait then till the english files are done.
I actually started thinking, would it be easy to convert a custom theme to Elkarte 1.1?
I know we try to keep things like this disabled but I think this is kind of standard.
In fact it was "just" a bug in the upgrade script. O:-)
I'd have resetted it via admin, the few ones who don't want them... They shall have one and disable it afterwards. Lol.
Sorry, missed that. :-[
hmm...Honestly I have no idea, maybe
@Spuds or
@Vekseid have a better view of how things have changed. O:-)
Hmm, my theme is heavily modified, I've removed many parts like menu and things like that, so I guess the update script would update anything but the places where the custom code was written?
You have a little error on your homepage:
Notice: Undefined index: is_mod in /.../forum/sources/Load.php on line 797
The upgrade from 1.0 to 1.1 is an overwrite of all the original files (including default theme), since you have created another theme it will not be touched, so you'll have to likely adapt your changes for the new things.
Cool, thanks for the explanation! In that case I will hold off with upgrading Elk :)
I'm unable to recreate the error.
It's in the home page, looks some kind of integration issue, feel free to open a topic so we can find the cause. ;)
@CrimeS the primary theme alterations are moving sprites and images into embedded CSS, along with some serious css cleanup. It involves tearing out a lot of hard-coded cruft.
The purpose is to make it easier to theme, in the long run.