The Serendipity Handbook

You can now read the (german) handbook here: PDF - https://github.com/s9y/Book (LaTeX source).

Forum-Information

Before posting about errors, make sure that the answer cannot already be found in our FAQ or by searching this forum!
Posting is restricted to registered users (registering is free and simple!) due to recent spam attacks. When having trouble with this board, contact garvin(-at)s9y(-dot)org.

Board index Upcoming Serendipity Features [1.7] Let's get rrready to rrr … elease

Mark threads with "[2.0]" for discussions about features in the longer-term future, "[1.6]" is for short-term. This is not the place for general discussions or plugin or template requests. Only features that are approved to happen by the core team should be listed here for better structuring.
User avatar
yellowled
Regular
 
Posts: 5541
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany

Postby yellowled » Tue Jan 08, 2013 8:37 pm

The release of 1.7 is coming up. Without actually setting a deadline just yet, everyone please check if there's still stuff in 1.7 which needs to be fixed in your “area of development” and report here if so.

This is basically to give Garvin an idea how much work needs to be done before actually considering a release, so it would be good if you could give a rough estimate as to how much time everyone needs to fix stuff.

YL

User avatar
Timbalu
Regular
 
Posts: 3724
Joined: Sun May 02, 2004 3:04 pm

Postby Timbalu » Tue Jan 08, 2013 9:14 pm

Does that really help opening another thread...? ;-)

none of these links really a showstopper - just some quickies:
viewtopic.php?f=11&t=19094 (add constants)
viewtopic.php?f=15&t=18876 (pimp spartacus - new dashboard feature request)
viewtopic.php?f=3&t=19056 (utf8 check)
viewtopic.php?f=10&t=19061 (pimp serendipity_event_smartymarkup)?
sorry, only 4 url links allowed here:
http:// board.s9y.org/viewtopic.php?f=10&t=18370&p=10433239#p10433239 (needs an answer to get "fixed" - new dashboard feature request)
http:// board.s9y.org/viewtopic.php?f=15&t=18176&p=10433205#p10433205 (2k11 discussion pending to be the new standard(-YL-)Template)

- wait for the smarty upcoming 3.1.13 release (Jan/Feb...?)
- check for other STRICT and fatal errors while using new PHP versions (i.e. ...Only variables should be assigned by reference)
- release a RC candidate without downgrading error reporting to production release behaviour (to fix as much as we can).
Regards,
Ian

User avatar
garvinhicking
Core Developer
 
Posts: 29471
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany

Postby garvinhicking » Sat Jan 12, 2013 7:52 pm

Timbalu wrote:Does that really help opening another thread...? ;-)


I don't have the time to read through all threads, so a simple pointer thread like this helps me a LOT. :)

http://board.s9y.org/viewtopic.php?f=11&t=19094 (add constants)


Should IMO be circumventable, see thread

viewtopic.php?f=15&t=18876 (pimp spartacus - new dashboard feature request)


I cannot offer to do this.



The s9y plugin files themselves are ISO-encoded, not UTF-8 - I think this is the reason.

http://board.s9y.org/viewtopic.php?f=10&t=19061 (pimp serendipity_event_smartymarkup)?


This indeed sucks. However I'm not deep enough into the Smarty3 stuff to understand why this no longer works :-(

http:// board.s9y.org/viewtopic.php?f=10&t=18370&p=10433239#p10433239 (needs an answer to get "fixed" - new dashboard feature request)


Should be a thing for 2.0 more than 1.7

http:// board.s9y.org/viewtopic.php?f=15&t=18176&p=10433205#p10433205 (2k11 discussion pending to be the new standard(-YL-)Template)


IMO should also be something for 2.0 instead of 1.7

- wait for the smarty upcoming 3.1.13 release (Jan/Feb...?)


Do you know if there is a release pending? I would like to release a RC for 1.7 definitely, as soon as I can find the time. Hopefully January->February. Once the RC is released, no Smarty3 upgrade should be performed. So I guess this is a question whether Smarty3 .1.13 is available before the day of the RC release. Ideally, the 1.7 RC is IMO more important than waiting for a Smarty3 change, what do you think?

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

User avatar
Timbalu
Regular
 
Posts: 3724
Joined: Sun May 02, 2004 3:04 pm

Postby Timbalu » Sat Jan 12, 2013 9:05 pm

garvinhicking wrote:Do you know if there is a release pending? I would like to release a RC for 1.7 definitely, as soon as I can find the time. Hopefully January->February. Once the RC is released, no Smarty3 upgrade should be performed. So I guess this is a question whether Smarty3 .1.13 is available before the day of the RC release. Ideally, the 1.7 RC is IMO more important than waiting for a Smarty3 change, what do you think?

No, I don't know any time in special. It was just a guess. If its there before, I'll push it.
Well, a possible Smarty bugfix release should not let us wait to push out a 1.7 RC. These pending bugfixes until now are just very rare cases (not really used by S9y) and don't change anything of the core features, as far as I know. So even a later addition to an already published RC should not really harm in my eyes!
Regards,
Ian

User avatar
Timbalu
Regular
 
Posts: 3724
Joined: Sun May 02, 2004 3:04 pm

Postby Timbalu » Sat Jan 12, 2013 9:17 pm

garvinhicking wrote:
http://board.s9y.org/viewtopic.php?f=10&t=19061 (pimp serendipity_event_smartymarkup)?


This indeed sucks. However I'm not deep enough into the Smarty3 stuff to understand why this no longer works :-(


I don't think it has something to do with Smarty3, as also happening prior. It is the (bad) limitation to not use any smarty delimiters (like in code samples a.s.o), which are not Smarty Tags, in any text body fields parsed by the smartymarkup plugin.
Regards,
Ian

User avatar
Timbalu
Regular
 
Posts: 3724
Joined: Sun May 02, 2004 3:04 pm

Postby Timbalu » Sun Jan 13, 2013 12:09 pm

I just remembered these (old) feature requests (viewtopic.php?f=15&t=17268):

Implement by core?:
  • find orphaned media items (lux)
  • delete multiple users at once (don)
Implement by Plugin?:
  • find entry-linked media items + sortable and pass to frontend (mattsches, lux)
  • check entry related external links for existence (lux)
Is that something for 1.7?

I addded multidelete images to 2.0 last May - should we backport that too?
Regards,
Ian

User avatar
yellowled
Regular
 
Posts: 5541
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany

Postby yellowled » Sun Jan 13, 2013 10:25 pm

Some minor things:

– I just updated 2k11 to the latest version in master and 2.0. I don't think there will be any more fixes until 1.7, 2k11 is pretty much “done” and only receives minor updates from time to time. So in terms of 2k11, we're good to go.

– Naming convention branches vs tags: As of now, we have a branch named “1.6” and a tag named “1.6”. I'm not a 100% sure, but I think this is what produces

Code: Select all
matthias at yl-mba in ~/GitHub/Serendipity on 2.0
$ git checkout 1.6
warning: refname '1.6' is ambiguous.
Switched to branch '1.6'

(because “1.6” could reference the branch or the tag). So maybe starting with 1.7, we should prefix the branch or the tag with “v”. I suggest to prefix the tags, but just because I guess we all type “git checkout 1.x” more often. :wink:

– To keep https://github.com/s9y/Serendipity/tags tidy, we might want to delete the v1.4 and svn tags at some point. I know it's basically nuts and bolts, but it would give us a cleaner download archive on GitHub. :)

YL

User avatar
garvinhicking
Core Developer
 
Posts: 29471
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany

Postby garvinhicking » Mon Jan 14, 2013 1:07 pm

Hi!

Ok, so I'll try to put the 1.7-RC1 (actually, simlpy 1.7-alpha1, for the error reporting...) online this week, is that okay? For better maintenance I'll only create the "1.7" branch and "t1.7" github tag for the actual final release, yes?

Best regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

User avatar
yellowled
Regular
 
Posts: 5541
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany

Postby yellowled » Mon Jan 14, 2013 1:49 pm

No objections from my end.

YL

User avatar
Timbalu
Regular
 
Posts: 3724
Joined: Sun May 02, 2004 3:04 pm

Postby Timbalu » Fri Jan 18, 2013 8:55 pm

Fine for me. Did you get my answers, Garvin?

Maybe its worth to rethink pushing the RC without setting it to production state, since we want some people to help us testing and who would like to push that to a poductive blog...? On the other hand I think the smarty change is pretty stable though, so our really need are some intensive PHP5.4 testers to get rid of the possible error_reporting notes still residing somewhere in the deep.
It would also work out to just post an official blog and forum text to help us testing an "anounced" master as "RC", zip a current master, rename alpha to RC1, remove the test dir, and offer that zip file, wouldn't it?!
Hmmm, I dont really know which way would be the best. Just wanted to mention it before weekend... Please, do what might be best in your eyes.

IMHO, tagging the release to "s9y-1.7" would be much nicer :wink:
Regards,
Ian

User avatar
yellowled
Regular
 
Posts: 5541
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany

Postby yellowled » Sat Jan 19, 2013 12:25 pm

Timbalu wrote:On the other hand I think the smarty change is pretty stable though, so our really need are some intensive PHP5.4 testers to get rid of the possible error_reporting notes still residing somewhere in the deep.

I've been running a test blog on 1.7 for months (because of the Uberspace subdomain issue), albeit not on PHP 5.4. It seems fairly stable. Then again, it's just a test blog.

YL

User avatar
garvinhicking
Core Developer
 
Posts: 29471
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany

Postby garvinhicking » Sat Jan 19, 2013 1:10 pm

Hi!

1.7-rc1 is here (non-production, so we should get our errors if they occur): http://blog.s9y.org/archives/243-Serend ... idate.html
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

User avatar
yellowled
Regular
 
Posts: 5541
Joined: Fri Jan 13, 2006 12:46 pm
Location: Eutin, Germany

Postby yellowled » Sat Jan 19, 2013 2:28 pm

FYI: Garvin just withdraw the 1.7RC1 due to an issue with older/deprecated plugins, e.g. browser compatibility, which will need to be fixed before the next RC.

YL

User avatar
garvinhicking
Core Developer
 
Posts: 29471
Joined: Tue Sep 16, 2003 9:45 pm
Location: Cologne, Germany

Postby garvinhicking » Tue Jan 22, 2013 11:21 am

Hi!

RC2 has now been posted. Keep the fingers crossed. ;)

Regards,
Garvin
# Garvin Hicking (s9y Developer)
# Did I help you? Consider making me happy: http://wishes.garv.in/
# or use my PayPal account "paypal {at} supergarv (dot) de"
# My "other" hobby: http://flickr.garv.in/

public s9y
Regular
 
Posts: 9
Joined: Tue Jan 22, 2013 1:38 pm

Postby public s9y » Tue Jan 22, 2013 1:49 pm

the following error occurs with followed links or page reloads on a local installation (OSX) updated to 1.7rc2, only direct access works well:

Code: Select all
Fatal error: Uncaught exception 'ErrorException' with message 'Serendipity error: stristr(): Empty delimiter' in /Users/me/Sites/serendipity/include/compat.inc.php:119
Stack trace:
#0 [internal function]: errorToExceptionHandler(2, 'stristr(): Empt...', '/Users/me/Sit...', 713, Array)
#1 /Users/me/Sites/serendipity/include/functions.inc.php(713): stristr('http://localhos...', '')
#2 /Users/me/Sites/serendipity/index.php(625): serendipity_track_referrer()
#3 {main}
  thrown in /Users/me/Sites/serendipity/include/compat.inc.php on line 119

Next


Return to Upcoming Serendipity Features

Who is online

Users browsing this forum: No registered users and 2 guests

cron