Skip to main content
EARLY Beta version of 2.0 Started by Administrator · · Read 316848 times 0 Members and 2 Guests are viewing this topic. previous topic - next topic

Re: EARLY Beta version of 2.0

Reply #135

Quote from: "Burke Knight" – Just going to wait until you post a beta installer before I test it....lol
That is a good idea LOL ... and soon-ish ;)

I did another push of updates this PM, really just some housekeeping tasks that needed to get done before the B1 package. 

The only "major" change was that I broke up the PM controller (note its still a  :poop: show) but getting better.  I pulled out labels, filters, reports, and searching to their own controllers.  Yes all of those functions were contained in the single gigantic pm controller.  At least now the various functions of PM are in their own controllers so updates and enhancements should be easier.  It cut the size of the primary controller in 1/2 which is good but its still way to long:man_shrugging:

Re: EARLY Beta version of 2.0

Reply #136

Another small bump ....

Update the emoji image packages to v16/v17 (unicode) they were at v14 ... so that added a few new ones.  Also chose to use GitHub naming for the :name: can't remember what was used the first time, but there are really no defacto standards ...

Fixed a strange dispatch path that allowed the dispatcher to maybe bypass the action controller which was not noticeable but could have some less than ideal side effects.

Fixed a couple of minor issues from the previous PM refactor (actually one issue was pre ElkArte) due to some wrong boolean math.  Ah well ... generally harmless.

OK back to getting the installer finished!

Re: EARLY Beta version of 2.0

Reply #137

Wonder if one fix broke the marking of notifications read function, as they wont clear now.

Re: EARLY Beta version of 2.0

Reply #138

Quote from: Burke Knight – Wonder if one fix broke the marking of notifications read function, as they wont clear now.
I'd say yes ... clears when you select the notification from the list but not when you click mark read .... easy fix.

I'm working on one of the last beta changes, reorganize the admin menu.  When I push that to the site I'll fix the notification item.

Re: EARLY Beta version of 2.0

Reply #139

Quote from: "Spuds" – I'd say yes ... clears when you select the notification from the list but not when you click mark read .... easy fix.
Should be fixed now ... this was a result of a previous change i made that enforced the dispatch and action sequence, better security.  That controller did things lazy and that is not supported any longer.  Could be other areas like that so be on the lookout!

Finished the admin menu update, man that was a lot of work and back and forth cuz really there is no one correct layout. Anyway its a lot better (i think at least)

All updates applied to site

Re: EARLY Beta version of 2.0

Reply #140

And another bump of the old site, getting closer to a B1 release.

This update continues to fix a few items from the Admin menu redo and more strict action processing
Like Stats has been removed from the top menu and is now an information center option just like site stats.
The click zone on the breadcrumbs was improved (actually just a class typo in the CSS)
A few installer tweaks, I've cleaned up the default options a bit so on a fresh install it makes a bit more sense.  Still lots of things for the admin to decide on.  I've run that a few times and seems good, now I'm installing addons to make sure nothing else was broken.

Re: EARLY Beta version of 2.0

Reply #141

Eagerly awaiting this release. 

Re: EARLY Beta version of 2.0

Reply #142

Got sidetracked updating SimplePortal so it was 2.0 compatible  Thought I was all done but found a couple of:bug:that needed fixing.  I'm sure there are more but that is always the case.  I did add a new goodie feature to the portal:partying_face:

OK now back to getting this release done!!:construction_worker:

 

Re: EARLY Beta version of 2.0

Reply #143

Made some good progress over the last few days.

I do have install working correctly, the only tweaks were getting the base settings to something more appropriate.

The upgrade was a different story, but I have it working to the point I can finally check on some refinements.  The delay was really in updating the update.php script so it worked with 2.0, plus there was so much old cruft in that file.  Anyway it now will upgrade a 1.1 db to a 2.0 version. 

If upgrading there is still manual work that needs to be done, copying attachments and avatars over but the script is not going to do that for you, the overall directory structure is just too different.  I'll jot down the easy path to upgrade but that will not be the only way, nor will the upgrade to anything other than update the db.

SO closer we inch !