[solved] Fatal Error on Upgrade?

Bloke · 2017-03-15 12:47:49

superbiate wrote #304750:

Some Textpattern files have been modified: /home/superb10/public_html/index.php,
/home/superb10/public_html/css.php

Why? Can you re-upload a clean copy? Edit: etc beat me to it.

superbiate wrote #304735:

Fatal error: Call to a member function start() on a non-object in /home/superb10/public_html/textpattern/publish.php on line 36

That’s the trace function getting mad. Normally due to a plugin, but in your case you don’t have any. Baffling, because on the front page of your site, it will have encountered the same thing but doesn’t issue an error. The only difference with the one in publish.php is that it’s referenced via the global $trace when it’s not explicitly defined as such in index.php.

My money’s on the css.php file. But failing that, a long shot: I wonder if PHP 5.4 is causing issues when we redeclare $trace as global in publish.php? I can’t see that being the issue, but remain open-minded. If so, I’ve no idea why it hasn’t occurred before.

Last edited by Bloke (2017-03-15 12:48:11)

colak · 2017-03-15 13:12:00

Bloke wrote #304766:

My money’s on the css.php file. But failing that, a long shot: I wonder if PHP 5.4 is causing issues when we redeclare $trace as global in publish.php? I can’t see that being the issue, but remain open-minded. If so, I’ve no idea why it hasn’t occurred before.

index.php has also been modified. I would upload it again too. It would be interesting to see how it has been modified.

Bloke · 2017-03-15 13:25:08

colak wrote #304767:

index.php has also been modified.

D’oh, how did I miss that! I scanned down, not across when I read that.

Okay, yeah, that’ll be it, because the new trace file won’t have been loaded. My guess is that, since both are listed as modified, they’ve simply been omitted when uploading them. Easy to miss updating those two in the site root.

superbiate · 2017-03-15 14:18:17

You guys are amazing: http://superbiate.com. YES, it was my failure to update the index & css files to root — huge d’oh!

Of course this now brings up a new message (but thankfully atop a working site)…

Tag error: <txp:rsd /> -> Textpattern Notice: tag is deprecated while_parsing_page_form: default, None
textpattern/publish/taghandlers.php:5025 trigger_error()
rsd()
textpattern/vendors/Textpattern/Tag/Registry.php:83 call_user_func()
textpattern/lib/txplib_publish.php:514 Textpattern\Tag\Registry->process()
textpattern/lib/txplib_publish.php:463 processTags()
textpattern/lib/txplib_misc.php:4476 parse()
textpattern/publish.php:562 parse_page()
index.php:105 textpattern()

Last edited by superbiate (2017-03-15 15:18:42)

Bloke · 2017-03-15 15:31:53

superbiate wrote #304769:

it was my failure to update the index & css files to root

Glad you got it working. Those two little files are easy to overlook.

Tag error: <txp:rsd /> -> Textpattern Notice: tag is deprecated

That’s easy to fix. Just find the <txp:rsd> tag in your site’s Pages/Forms and remove it. Might I suggest the plugin smd_where_used? If you install and enable it, then visit the Extensions panel you’ll be able to use that to search your site’s templates for matches. The plugin looks a bit tired now as it needs bringing up-to-date with the latest 4.6.2 visuals, but it still works.

superbiate · 2017-03-15 16:31:20

Dear gents, thank you all very kindly for the help: Where Used is the one and only plugin on a perfectly functioning, fresh 4.6.2 upgrade. Debug mode renders a clean site without error, and production status is live. As I dig into updating this web presence I’ll do so glad to be part of this excellent Textpattern community. Cheers!

colak · 2017-03-15 16:48:34

Unless you are actually using some sql magic or visit phpMyAdmin very often, I would also install rss_admin_db_manager as it will help you in repairing and backing up your database. A word of warning: drop=delete!

uli · 2017-03-15 17:32:18

colak wrote #304773:

I would also install rss_admin_db_manager

Good nudge for expanding the first post of the rss_db_man topic by the 4.6.2 compatible versions at the end of the thread (done).

Glad the website is up again, superbiate. (Some inspiring articles, BTW!)

Last edited by uli (2017-03-15 17:35:35)

superbiate · 2017-03-15 17:36:53

Which version is the one shown at http://www.kreatore.it/?rah_plugin_download=rss_admin_db_manager, yes? Asking only because I’ve just installed it, but see no new tabs in admin as expected…

uli · 2017-03-15 17:39:00

superbiate wrote #304775:

but see no new tabs in admin as expected…

If all is good, you’ll have a new top level tab named Extensions, now.

superbiate · 2017-03-15 17:41:31

Aye – and it only shows Where Used. Curious…

uli · 2017-03-15 17:56:41

superbiate wrote #304777:

Aye – and it only shows Where Used. Curious…

Yup.

Hmhm. You’ll have activated it (better safe than sorry). Do you have publisher rights? (See “Role” on Admin > Users.) Else I have no idea other than trying the Bloke version.

Textpattern CMS

Textpattern CMS support forum

#13 2017-03-15 12:47:49

Re: [solved] Fatal Error on Upgrade?

superbiate wrote #304750:

superbiate wrote #304735:

#14 2017-03-15 13:12:00

Re: [solved] Fatal Error on Upgrade?

Bloke wrote #304766:

#15 2017-03-15 13:25:08

Re: [solved] Fatal Error on Upgrade?

colak wrote #304767:

#16 2017-03-15 14:18:17

Re: [solved] Fatal Error on Upgrade?

#17 2017-03-15 15:31:53

Re: [solved] Fatal Error on Upgrade?

superbiate wrote #304769:

#18 2017-03-15 16:31:20

Re: [solved] Fatal Error on Upgrade?

#19 2017-03-15 16:48:34

Re: [solved] Fatal Error on Upgrade?

#20 2017-03-15 17:32:18

Re: [solved] Fatal Error on Upgrade?

colak wrote #304773:

#21 2017-03-15 17:36:53

Re: [solved] Fatal Error on Upgrade?

#22 2017-03-15 17:39:00

Re: [solved] Fatal Error on Upgrade?

superbiate wrote #304775:

#23 2017-03-15 17:41:31

Re: [solved] Fatal Error on Upgrade?

#24 2017-03-15 17:56:41

Re: [solved] Fatal Error on Upgrade?

superbiate wrote #304777:

Board footer