Serendipity Forums

Have not tried Ian's new version, but last night I tried upgrading an existing s9y test installation to 2.0, and I am getting a white page with a title of "== TESTING ERROR MODE == " followed by the output of every single array. What's up with that?

???
Well, at least the first array lines or the exception Fatal error lines at the end would be needed to know what happened.

Very end is:

That says:
The event plugin serendipity_event_forgotpassword.php method (function) event_hook(...) call needs to be fully compat with the origin core function. As far as I remember Grischa has solved this for every event plugin in additional_plugins. As you have serendipity_event_forgotpassword there, it seems this is not an official plugin, or you did not upgrade to its new version. The line has to look like:

I merely copied the 2.0 files to an existing s9y installation. When I remove the plugin from the database, I get the same error for the next plugin in the table. Are you saying every event plugin has to be upgraded before upgrading s9y core to 2.0?

No, I say, if using a testing developer version like 1.7 or 2.0, you have a more strict error reporting, as this is testing, not release. If it is testing, you should at least have the latest state for all files used. This means also all files installed via additional_plugins. And I can say, these kind of errors did touch a lot of files. Its only something the error reporting and the php version wants us to be strict for the future!
So basically "Nearly, Yes!" is the answer!

I finally have a working 2.0 install with YL's latest changes. @YL - is there anything you are NOT working on just yet? You seem to be modifying many files every day. Also, is there any specific logic you are following with your modifications?

Don Chambers wrote:is there anything you are NOT working on just yet? You seem to be modifying many files every day.

That seems about right.

I prefer to use lots of small commits (and I recommend everyone do the same because it really doesn't help to change a lot in one commit), which is probably why it seems way more than it actually is.

Don Chambers wrote:Also, is there any specific logic you are following with your modifications?

Well, I spend yesterday and today mostly finishing the conversion to HTML5, although it is not “much” HTML5 just yet but merely proper, up to date markup. Most of this stuff hasn't been touched in ages, and it shows.

This goes along with a lot of quality assurance, i.e. removing inline CSS and JS (where possible without – hopefully – breaking anything), rearranging attributes so the markup is consistent, etc. Sometimes, something will cross my mind while I'm working at something else (which is probably why you don't see a specific logic), also Ian has been finding some last-minute bugs which needed to be worked in inbetween changes. Then there's the occasional commit which is necessary just because I'm not that skilled with git yet and need to revert my changes in a weird way.

I also managed to rewrite most of the markup for the media db today. It's still quite a mess, but that's mostly because the media db's JS is pretty complicated and requires a specific markup to work at some points (which means I can't change the markup there, but that's only one tpl file).

I guess it's a wrap for now in terms of markup, so I'll try and get started on a very basic design tomorrow so we'll have something decent to look at and discuss in the next developer sprint.

YL

I''l start with your latest admin/index.tpl and see if I can come up with any inspiration.

Just a heads up: I didn't really get to styling the backend yet, some client work changed my schedule for today. What I have committed/am committing also is merely trying it on for size. It might (and likely will) end up looking very different, especially since there might be some layout/usability changes we need to discuss further before actually implementing them.

YL

yellowled wrote:I didn't really get to styling the backend yet, .... What I have committed/am committing also is merely trying it on for size.

But as I have seen this morning, you are doing a fucking good job!!! THUMBS UP!

The thing is, when I actually get around to designing stuff, I look under the hood and find stuff that still needs to be fixed in the markup. Very annoying. I haven't even gotten around to just trying to understand the JS yet, let alone port it to jQuery.

It's like I posted on Twitter a few days ago: this is going to be much, MUCH more work than anyone of us is aware now …

YL

I noticed that when working with the PoC Dashboard...
If you need some help with it, drop a note.
And what about all these left alone br linebreaks, which I dimley remember still to be in core... Isn't this something we should switch off with your new code?

Timbalu wrote:If you need some help with it, drop a note.

Well, it would really help if someone with a better knowledge of native JS than me went over all the JS stuff and maybe documented what it actually does.

Timbalu wrote:And what about all these left alone br linebreaks

Good point, that's another thing I should grep for.

YL

I am also working on some backend design as I am not sure what else to work on. One immediate question - are we continuing to use the Nuvola icon set, or should we consider something else?