Feedback to: Textpattern CMS 4.6.0 beta released

jakob · 2016-06-20 13:13:25

Destry wrote #299870:

Not only installed Sequal Pro (excellent app, thank you), but updated installs of mysql and php too. Fresh oil!

Yes, Sequel Pro makes it all a little bit easier, and not just on the eyes.

I’m not exactly sure what your suggesting, but if I look in the txp_prefs table, at key prefs_idx, and column name, the value there is pane_article_textfilter_help_visible. Nothing appears to be duplicate to me.

I think he means, rename the key currently called pane_article_textfilter_help_visible to the new name pane_article_textile_help_visible. You should be able to edit that in place with Sequel Pro.

In fact, that error seems to have gone away, but is replaced by a new one:

User_Error "Invalid default value for 'Posted'" in /Users/me/Sites/evilplans/textpattern/lib/txplib_db.php at line 405....

I’m no expert here, but that sounds like something hasn’t run quite right with your update script as some of the datestamp defaults have changed. I wouldn’t have thought that would effect the Posted column as much as the Modified column, so perhaps check in Sequel Pro to see if you have any strange values in the “Posted” column of the textpattern table. Perhaps there’s some anomaly or zero date in there?

Bloke · 2016-06-20 13:18:37

jakob wrote #299872:

I think he means, rename the key currently called pane_article_textfilter_help_visible to the new name pane_article_textile_help_visible.

Other way round! The new name is pane_article_textfilter_help_visible :-)

Destry · 2016-06-20 13:26:41

Bloke wrote #299873:

Other way round! The new name is pane_article_textfilter_help_visible :-)

OK. I actually have a record for each one, so maybe that’s where the duplicate error was coming from?

So I should delete the row for “textile_help”, then.

Bloke · 2016-06-20 13:34:24

Destry wrote #299874:

I should delete the row for “textile_help”, then.

Yep. Since ‘textile’ could now be any textfilter in use.

Destry · 2016-06-20 14:33:17

jakob wrote #299872:

that sounds like something hasn’t run quite right with your update script as some of the datestamp defaults have changed.

I just walked through the update again and reloaded the dump file. Still get the same error. Checking the Posted field’s default value gives: 0000-00-00 00:00:00, and all values in actual content records have that pattern, but actual/valid dates per article.

But I just did an install for a different site — new database and no content — and I get this error, stuck in the Languages panel:

User_Error "Truncated incorrect date value: '0000-00-00'" in /Users/me/Sites/other/textpattern/lib/txplib_db.php at line 405.

And…

textpattern/lib/txplib_misc.php:1677 adminErrorHandler()
updateErrorHandler()
textpattern/lib/txplib_db.php:405 trigger_error()
textpattern/lib/txplib_db.php:433 safe_query()
textpattern/update/_to_4.6.0.php:253 safe_delete()
textpattern/update/_update.php:84 include()
textpattern/index.php:180 include()

Seems to be something somewhere.

Bloke · 2016-06-20 15:58:49

Destry wrote #299877:

I just did an install for a different site — new database and no content — and I get [Truncated incorrect date value: 0000-00-00] error, stuck in the Languages panel

You’re not the only one. Which MySQL version are you using?

See also: forum.textpattern.com/viewtopic.php?id=46973 and github.com/textpattern/textpattern/issues/694 for more info.

A fix needs to be devised, so any feedback you may have by tinkering with the above linked information would be incredibly valuable to achieve such a fix, thanks!

Destry · 2016-06-20 17:27:31

I have to step away from it for a while now, but I will do as you suggest, Bloke.

Yesterday I was running:

mysql 5.6.23
php 5.5

That worked fine until I updated a local install with Txp 4.6beta. That’s when I reported the first round of errors.

Today, after installing Sequal Pro and making a dump of all my local DBs, I decided to update mysql too. There’s a bit of a story there, but long story short I’m now running mysql 5.7.13 under Homebrew. After installing, I was getting a “CAVEAT” on the command-line that there was a conflict with /etc/local/my.cnf, which was a derelict file from an older mysql install, I think, because Homebrew installs its entire mysql package at /usr/local/Cellar/. Anyway, I deleted the offending my.cnf. I don’t know if that was a good thing or bad yet.

After updating mysql, the original error went away about the textile/textfilter thing, but not because it fixed the problem. I still had a record for both items in the table. But the error wasn’t showing anymore regardless.

Instead, it was showing the new error about Post dates.

I also updated php today. I normally let the newest OS version of mac handle that, but I wanted php7 (which isn’t in El Capo) so I did it straight from php.net with their Mac package. I’m now getting all kinds of errors but I think part of the problem is I don’t have everything hooked up right.

My phpinfo.php file says I’m now running php 7.0.7, but the command-line isn’t seeing the same thing:

php -v
PHP 5.5.34 (cli) (built: Apr 22 2016 19:16:58) 
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies

I used this instruction to update php, but I’m confused by it because the last part says to “undo” what the update does, but if I do what it says, it reverts back to the previous php I was running. I probably need some guidance there.

Whatever the case, I now get these errors when trying to access a local Txp site that has NOT been updated to 4.6beta. This is what’s shown on the login screen before I can even login…

( ! ) Deprecated: Methods with the same name as their class will not be constructors in a future version of PHP; DB has a deprecated constructor in /Users/me/Sites/webapp/textpattern/lib/txplib_db.php on line 23

Call Stack
#	Time	Memory	Function	Location
1	0.2501	402264	{main}( )	.../index.php:0

( ! ) Fatal error: Uncaught Error: Call to undefined function mysql_connect() in /Users/me/Sites/webapp/textpattern/lib/txplib_db.php on line 34
( ! ) Error: Call to undefined function mysql_connect() in /Users/me/Sites/webapp/textpattern/lib/txplib_db.php on line 34
Call Stack
#	Time	Memory	Function	Location
1	0.2501	402264	{main}( )	.../index.php:0
2	2.2156	1163512	include( '/Users/me/Sites/webapp/textpattern/lib/txplib_db.php' )	.../index.php:78
3	2.2156	1163584	DB->DB( )	.../txplib_db.php:50

So I seem dead in the water whether I use 4.6beta or otherwise at the moment.

In summary, currently running:

mysql 5.7.13
php 7.0.7

My php hook up is questionable at the moment. But I don’t know where to start looking to verify.

jakob · 2016-06-20 18:28:10

Bloke wrote #299873:

Other way round! The new name is pane_article_textfilter_help_visible :-)

Mea culpa!

Destry · 2016-06-20 18:33:37

Destry wrote #299879:

My phpinfo.php file says I’m now running php 7.0.7, but the command-line isn’t seeing the same thing

I see now that part is normal behavior according to the source of the php7 package. They don’t overwrite Apple’s own binaries, which is probably smart considering the Sierra upgrade that’s coming. So I just need to add a path in my .profile, or whatever. And that have their own .ini file which I’ll look closer at after dinner too.

gomedia · 2016-06-20 23:51:41

philwareham wrote #299867:

All this simplified install conversation, whilst interesting, needs to be moved to Textpattern 4.7 target, since a beta is not the place to be making substantial changes to the installation process. Please can someone open an issue for this topic at the repo and I will flag it as 4.7 proposed work, for discussion there.

Is done – Issue 713

Destry · 2016-06-21 06:06:59

Destry wrote #299879:

I now get these errors when trying to access a local Txp site that has NOT been updated to 4.6beta.

Ah. I forgot about Ruud’s warning, so that may explain the error with installs not updated to 4.6beta yet. I’ll get them all updated then continue the quest.

Destry · 2016-06-21 07:48:31

Bloke wrote #299878:

github.com/textpattern/textpattern/issues/694

Your mods worked for me too on the “Truncated incorrect date value: ’0000-00-00’” error.

But not for the “Invalid default value for ‘Posted’” error. In this case, it appears the problem is I have default DATETIME values in the textpattern table as 0000-00-00 00:00:00, when those default values should just be empty fields. Likewise the one DATE value should also be empty instead of 0000-00-00

I say that because for the local site your mods fixed, the fields are empty and the site has no further errors.

However, I can’t seem to edit those default values using Sequal Pro, it won’t let me, which might be my unfamiliarity with SP.

Textpattern CMS

Textpattern CMS support forum

#109 2016-06-20 13:13:25

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Destry wrote #299870:

#110 2016-06-20 13:18:37

Re: Feedback to: Textpattern CMS 4.6.0 beta released

jakob wrote #299872:

#111 2016-06-20 13:26:41

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Bloke wrote #299873:

#112 2016-06-20 13:34:24

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Destry wrote #299874:

#113 2016-06-20 14:33:17

Re: Feedback to: Textpattern CMS 4.6.0 beta released

jakob wrote #299872:

#114 2016-06-20 15:58:49

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Destry wrote #299877:

#115 2016-06-20 17:27:31

Re: Feedback to: Textpattern CMS 4.6.0 beta released

#116 2016-06-20 18:28:10

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Bloke wrote #299873:

#117 2016-06-20 18:33:37

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Destry wrote #299879:

#118 2016-06-20 23:51:41

Re: Feedback to: Textpattern CMS 4.6.0 beta released

philwareham wrote #299867:

#119 2016-06-21 06:06:59

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Destry wrote #299879:

#120 2016-06-21 07:48:31

Re: Feedback to: Textpattern CMS 4.6.0 beta released

Bloke wrote #299878:

Board footer