Topic: No Shoutbox Possible After Upgrade To SP 2.3.4

[newtoallthis]

Have just upgraded to SP 2.3.4 on my test forum. I chose the option to retain data in the hope that my custom boxes would show after the reinstall....which most did.

The only missing item was the shoutbox, so I created a new one and tried to add it to site using the Add Block panel. The new shoutbox cannot be 'seen' in Add Block. I'm getting the message that a shoutbox hasn't been created.

It may be relevant that I previously edited my SMF default profile to display a shoutbox with a textarea input rather that a single text inut line.

That edit is referred to in the following thread http://simpleportal.net/index.php?topic=8544.0

[newtoallthis]

Not sure whether it's relevant to the missing shoutbox, but there are other custom blocks missing (moral, check carefully before jumping in with both feet!).

They are, 'Recent Posts', 'Calendar', 'User' & 'Who's Online'.

I've not tried to recreate these, yet, it's the fact that the shoutbox cannot be created that bothers me.

[newtoallthis]

Sorry for wittering on, but I'm adding information as I am finding it.

In the Blocks List, all 'missing' blocks are listed and shown as active, but are not visible in the forum.

Have tried uninstalling 2.3.4 (inc. remove data) and reinstalling. No joy. Some blocks will install 'randomly' on the front page but aren't visible in the forum.

[slop_chute]

Did you double check your permissions for each block. They might be getting reset for your blocks if your using the preview.  Just a thought.. Since you indicate some of the blocks are active and not viewable.

http://simpleportal.net/index.php?issue=451.0

[newtoallthis]

Thanks for getting back. I think I've solved the problem but I can't tell you why it seemed to work.

I decided to uninstall the 2.3.4 version and start again. However, after re-installation, various artefacts of the 2.3.3 installation were still showing in the blocks list although they couldn't be activated (inc. my shoutbox).

So, I deleted all custom blocks that I'd created, uninstalled SP 2.3.4, deleted the 2.3.4 package, emptied the cache and reinstalled SP 2.3.4.

This time, SP is behaving as it should. It will let me create a shoutbox and then to enable it in a new block. I just then have to edit PortalShoutbox.template.php in my default theme to exchange the text input for a textarea (just my preference), and all is well.

Sadly, to upgrade from 2.3.3 to 2.3.4 will mean remaking the 17 blocks I have enabled on my main forum (and making sure that I opt for 'everywhere' and 'members' on each occasion).

I'm guessing that the Holy Grail for [SiNaN] would be to be able to create a Firefox style Profile for use with SP in order to make upgrading seemless whilst avoiding the hassle normally encountered on each major upgrade. Not being too critical, though, because from what I've seen so far, SP is the best option out there for adding functionality to SMF.

[slop_chute]

Not sure what your talking about with firefox. I use that browser and have done hundreds of installs  with SMF and SP with no issues like your describing. I would suspect you your forum has a hitch somewhere with mods or a path issue. Possibly not taking note of the errors in the package manager.  You did mention that you edited files, but I don't know what that is about and you probably should of removed your edit before upgrading (normalize the 2.3.3 installation).   Anyway That is beside the point .. You got it fixed. 

[Eliana Tamerin]

Unfortunately, situations like yours are not always as simple as they seem. Sometimes the script (SP) can be behaving correctly while the server does not, which can corrupt databases, prevent their removal or complication installations like yours. Web hosting is, and likely will always be, a hodgepodge of mix/matched technologies that, when balanced properly, will deliver a flawless environment but can be knocked out of whack with the slightest tap.

Regardless of the cause, it sounds to me like this is resolved for the most part? If this is the case, just click the [Topic Solved] button on the bottom of this page or let me know and I will do it. If not, is there anything else that needs resolving?

[newtoallthis]

Not sure what your talking about with firefox. I use that browser and have done hundreds of installs  with SMF and SP with no issues like your describing. I would suspect you your forum has a hitch somewhere with mods or a path issue. Possibly not taking note of the errors in the package manager.  You did mention that you edited files, but I don't know what that is about and you probably should of removed your edit before upgrading (normalize the 2.3.3 installation).   Anyway That is beside the point .. You got it fixed. 

No problem with Firefox.

What I was alluding to is the desirability for software to upgrade with as little fuss as possible.

Firefox is great because even when carrying out a major upgrade, user settings, extensions, plugins etc. are not overwritten in the process. They are retained in your user 'profile'. This obviates the need to get FF back how you like it after an upgrade. Essentially, its appearance and pre-upgrade functionality has not been lost.

Sadly (and I understand that SP and SMF developers don't have the resources of the Mozilla Corp!), almost every upgrade results in the need to reinstall mods and recreate blocks.

[newtoallthis]

Unfortunately, situations like yours are not always as simple as they seem. Sometimes the script (SP) can be behaving correctly while the server does not, which can corrupt databases, prevent their removal or complication installations like yours. Web hosting is, and likely will always be, a hodgepodge of mix/matched technologies that, when balanced properly, will deliver a flawless environment but can be knocked out of whack with the slightest tap.

Regardless of the cause, it sounds to me like this is resolved for the most part? If this is the case, just click the [Topic Solved] button on the bottom of this page or let me know and I will do it. If not, is there anything else that needs resolving?

I will wait until after reinstalling all blocks before classing this as resolved.

A question. Should uninstalling SP 2.3.3 then installing 2.3.4  have removed all custom blocks from my forum? Should it be necessary to delete non-default blocks prior to upgrade?

[Eliana Tamerin]

If you're running SMF 2.0? Then no, it shouldn't. There should be a check mark when uninstalling mods, if you do not check it, then your database information (blocks and so forth) should not be lost. This should be unchecked by default.

[newtoallthis]

As I wrote earlier in this thread, I have previously edited PortalShoutbox.template.php using SMF's 'Modify Themes' to force my shoutbox to display a textarea as opposed to single line text input box.

That edit is referred to in the following thread http://simpleportal.net/index.php?topic=8544.0 .

Would it be wise to revert this to the default PortalShoutbox.template.php code prior to upgrade?

[simondale]

I seem to be having the same problem with a fresh upgrade from SMF v1.11.11 to v2.0.2 and Simple Portal v2.3.4.  I can't get the Shoutbox to appear at all.

[AngelinaBelle]

When you upgrade SimplePortal, you will get all new shoutbox templates, so your changes will be lost.
You can try them again afterwards.