Issue with CMS Widgets not showing content on frontpage just blank edit box

[CozmicShredder]

Using vBulletin 4.2.2

I was hoping someone else had this issue and knows a quick fix but seems whenever I create or edit a Static HTML widget it appears as a black edit box

[Lynne]

What did you enter into the "Enter Static HTML" box in the Configuration page?

[CozmicShredder]

What did you enter into the "Enter Static HTML" box in the Configuration page?

hey Lynne I forgot about this post...

I am still having this issue anytime I make a custom block or edit a block. Even if I open an old block and re-save it without editing I have the same issue with it...

For instance

My UStream Block:
<center><iframe src="http://www.ustream.tv/embed/9983863" width="420" height="240" scrolling="no" frameborder="0" style="border: 0px none transparent;"></iframe><br /><a href="http://www.ustream.tv/" style="padding: 2px 0px 4px; width: 400px; background: #000000; display: block; color: #FFFFFF; font-weight: normal; font-size: 10px; text-decoration: underline; text-align: center;" target="_blank">Video streaming by Ustream</a></center>

It actually worked fine until I resaved it... The code never changed either way from before I saved it until after so nothing is being changed from saving it in the CMS widgets...

[CozmicShredder]

Any help from anyone I am still getting this issue with any Static HTML block I make or edit! I tried to reload the 4.2.2 upgrade from vBulletin to see if something went wrong with the 4.2.2 update but nothing fixed it! I also tried clearing cache and disabling hooks from the admincp and from the config... it just seems to be effecting the Static HTML... Tried the Tools.php almost everything I can think of...

I think it's happening from the AdminCP in the Widget creation or Edit...

[BirdOPrey5]

Have you tried re-creating the widget?

[CozmicShredder]

Have you tried re-creating the widget?

Yes over and over it's not just any particular widget it's any Static HTML widget same issues new or old or recreated!!

[CozmicShredder]

I thought it was the .htaccess file so I removed it same thing happened... I am wondering if it is 4.2.2 that is when it started after the update... Something might not have updated correctly am not sure... I most likely will have to wipe the cms but would hate to reload all the custom stuff I made without know what happened..

[Lynne]

Create a new style with no parent:

• Styles & Templates > Style Manager > Add New Style
• Parent Style: No Parent Style
• Title: Default vBulletin
• Allow User Selection: Yes
• Save

Then browse that page using that totally default vbulletin style - do you still have the same problem?

[CozmicShredder]

Create a new style with no parent:

• Styles & Templates > Style Manager > Add New Style
• Parent Style: No Parent Style
• Title: Default vBulletin
• Allow User Selection: Yes
• Save

Then browse that page using that totally default vbulletin style - do you still have the same problem?

I did that then removed the staticHTML blocks remade them same issue

[CozmicShredder]

I really wished I understood the dynamics of the vbulletin product so I could easily determine what causes issues! I would think maybe not you but people that make the vbulletin would just know what is causing this particular error or how to remedy it easily... It almost feels like any group that makes anything thinks there are way to many variables but if you consider how to get the CMS back to the beginning or have a way to verify the integrity of the product it should be a simple fix??

[BirdOPrey5]

The upgrade from 4.2.1 did not make any database changes or change any templates so it doesn't make much sense to us either why the upgrade would cause this issue. If you re-upload the 4.2.1 files over your 4.2.2 files (do not run any upgrade script) does the problem go away? If not please re-upload the 4.2.2 files again.

[CozmicShredder]

The upgrade from 4.2.1 did not make any database changes or change any templates so it doesn't make much sense to us either why the upgrade would cause this issue. If you re-upload the 4.2.1 files over your 4.2.2 files (do not run any upgrade script) does the problem go away? If not please re-upload the 4.2.2 files again.

Thanks for the idea Joe I never thought to try that one but it didn't work... This is really starting to piss me off will have to dump my cms but am seriously curious what is the root cause of it... Once I know it I can easily fix it if it happens again that's just OCD of my mind... I am wondering all kinds of issues that could cause it like the datastore, something with goDaddy, rouge ,htaccess file somewhere... PHP version...

Nothing else seems broken with the CMS other than StaticHTML vbCMS Widget but it only happens when I create a new one or modify an existing one. That should be a huge clue for someone who is knowledgeable or I would think... I'll leave the hooks on and disable every plugin or module I have... You know it would be neat if VB added a simple way to disable a group of Products and or Plugins at the same time other than just using Disable hooks... Like the one click button same as the one in the (Repair / Optimize Tables) to shut them all off??

[BirdOPrey5]

Can you post a link or PM me a link to the forum so I can see it happening? Maybe will have more / better ideas.

[CozmicShredder]

My website is www.cozworld.com I PM'd you as well didn't see you asked for it here as well... I had it in my profile no secret stuff with me...

I think it was a Product after all but not sure which one or why when I disable each one http://www.cozworld.com then I deleted one of my StaticHTML widget's and recreated it and it worked but when I disabled the Hook system through the settings it would screw up the StaticHTML widgets... So I guess I should use the includes/config.php to disable it for completely stopping the hooks or is the Hooks disable in the admincp settings the same??

Either way I still would like to hear what you think about it.

[BirdOPrey5]

When I view your site it's all working now... yes disabling via config.php is the better/safer way of disabling all hooks. Disabling via Admin CP settings works often but not always.

Any idea what mod was the problem? Really like your style BTW.