Announcement

Collapse
No announcement yet.

Problem when updating content.

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • ashley76
    replied
    Originally posted by Mystics View Post
    Edit the file /vb/cache/db.php and search for:
    Code:
    			else
    			{
    				if (!$obj->isExpired())
    				{
    					$found[$record['cacheid']] = $record['data'];
    				}
    			}
    Replace it with:
    Code:
    			else
    			{
    				$obj = new vB_CacheObject($record['cacheid'], $record['data'], $record['expires'], $record['locktime']);
    				if (!$obj->isExpired())
    				{
    					$found[$record['cacheid']] = $record['data'];
    				}
    			}

    While this may fix this particular problem, this fix causes another big one... After applying the code change, I could no longer post new articles. I had an article ready to publish and published it, but the article came up blank and said not published. So I tried editing the article and everything I typed was in there, but again after trying to publish it it would show up blank and not published...

    After reverting the db.php to its original, the article published with no problem...

    This is a major problem for me and needs to be fixed soon...

    Leave a comment:


  • Micronichos
    replied
    I had the same problem and applied this fix, will this change be included in 4.0.5 ?

    Leave a comment:


  • xabo
    replied
    Ok, saved it now.. hopefully the problem wont come back.. ill report back if so

    Leave a comment:


  • Michael König
    replied
    Edit the file /vb/cache/db.php and search for:
    Code:
    			else
    			{
    				if (!$obj->isExpired())
    				{
    					$found[$record['cacheid']] = $record['data'];
    				}
    			}
    Replace it with:
    Code:
    			else
    			{
    				$obj = new vB_CacheObject($record['cacheid'], $record['data'], $record['expires'], $record['locktime']);
    				if (!$obj->isExpired())
    				{
    					$found[$record['cacheid']] = $record['data'];
    				}
    			}

    Leave a comment:


  • xabo
    replied
    Any ETA on when this issue can be fixed? Quite annoying that we need to "Clean CMS Cache" all the time

    Leave a comment:


  • MichaelDeMille
    replied
    I just reported it.
    http://tracker.vbulletin.com/browse/VBIV-7835

    Leave a comment:


  • Michael König
    replied
    Please report it as a bug and provide a link to this thread as reference:
    http://tracker.vbulletin.com/

    Leave a comment:


  • vikris
    replied
    It's no use of clearing the cms cache. The error starts again after a while.

    Leave a comment:


  • athlon64bit
    replied
    If it hasn't already this needs to be reported as a bug I think.

    Leave a comment:


  • calvingarfield
    replied
    clear cms cache

    same error, gone after clearing cms cache.

    Leave a comment:


  • vikris
    replied
    True, I have this error also randomly when saving an article or editing. This is introduced in vb 4.0.4

    Leave a comment:


  • Astyanax
    replied
    I have the same problem.

    Leave a comment:


  • MichaelDeMille
    replied
    I'm having the same problem. I cleared my cache yesterday, which fixed the problem, but this morning there it was again.

    Leave a comment:


  • Sfitzgerald
    replied
    i just had the issue one time after I upgraded and cleared my cms cache and it went away - Have not seen it again since the first time

    Leave a comment:


  • athlon64bit
    replied
    This problem returned for me. I cleared the cache to fix it. Unfortunately as I have to sleep and cannot keep refreshing the page every 15 minutes to see if forum has went down due to this error I have had to disable the CMS feature. Can someone explain what the problem is? Is it a bug? I did not have this issue on vb 4.0.3.

    Leave a comment:

widgetinstance 262 (Related Topics) skipped due to lack of content & hide_module_if_empty option.
Working...
X