Announcement

Collapse
No announcement yet.

Have to use Clear CMS Cache to display new articles and comments

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

  • J BO$$
    replied
    I have this problem and it WILL not work for me neither does the forum side bar, and we bought vb suite which aint cheap.We are running 4.1.9 so i will submit a ticket and for the $ spent,i hope it to be solved ASAP.Many other problems as well, didnt have these problems before the upgrade to 4.1.9

    UPDATE: I have to give vb staff props for they have come in and done more than enough to try to resolve my problems when come to find out after talking to my server people that a server crash may be the problem.Thanks to big JOE D
    Last edited by J BO$$; Sun 8th Jan '12, 12:43am. Reason: Vb staff is on their A-Game

    Leave a comment:


  • Bram
    replied
    So we are now almost two year further in time. This problem exists already since december 2009 for me and every freakin day i have to manually clear the cms cache.

    Currently we are running 4.1.5 software AND THE PROBLEM GOT REPORTED AGAIN by our users!

    I am so close to give up on this **** really and migrate to wordpress with xenforo! Unbelievably frustrating!

    Leave a comment:


  • fwulfers
    replied
    I am on 4.1.4 and have had this problem with all versions since we started using the vB software last year. It really is getting annoying having to clear the cache several times a day. Any fixes for this yet? Sometimes new comments are showing up but most of the time the CMS cache has to be cleared first.

    Leave a comment:


  • Snakefrancesco
    replied
    I have the same problem:

    https://www.vbulletin.com/forum/showthread.php/382724-VBSEO-and-recent-comment-widget-problem

    How can I fix it?

    Leave a comment:


  • Bram
    replied
    This has been reported by so many people in the past. Running vb4 since the first release and have this issue from the beginning. Everytime they say they will fix it but nothing happens. Getting so fed up with this obsolete software, but we are forced to continue vbulletin for now because of the vbseo and downloads2 modifications we run on our site.

    Instead of creating useless mobile suites and other customizable profile pages nobody asked for the devs should focus on fixing the bugs in their software.

    Leave a comment:


  • reefland
    replied
    I was just looking back through my old tickets and I have actually brought this up in a few tickets going back as far as 4.0.2.

    Leave a comment:


  • reefland
    replied
    It is in there. Creating ticket now.

    Leave a comment:


  • Edwin Brown
    replied
    Originally posted by reefland View Post
    Edwin,

    Do you need a support ticket still?
    Could you please do one thing first?

    You're at 4.0.8. That's now five versions back. If you can look at your version of the file /packages/vbcms/content/article.php.


    Search for the string "public function getInlineEditBodyView"

    A few lines above it you should see this:


    vB_Cache::instance()->cleanNow();
    $this->content->reset();
    //reset the required information
    $this->content->requireInfo(vBCms_Item_Content::INFO_BASIC);
    $this->content->requireInfo(vBCms_Item_Content::INFO_CONTENT);
    $this->content->requireInfo(vBCms_Item_Content::INFO_CONFIG);
    $this->content->requireInfo(vBCms_Item_Content::INFO_NODE);
    $this->content->requireInfo(vBCms_Item_Content::INFO_PARENTS);
    $this->content->invalidateCached();

    If you don't see it, then you have an obsolete version. Please update when you can. If you do see this, then yes- please create a support ticket.

    Leave a comment:


  • reefland
    replied
    Edwin,

    Do you need a support ticket still?

    Leave a comment:


  • Bram
    replied
    Exactly what reefland describes.

    Leave a comment:


  • Edwin Brown
    replied
    Originally posted by reefland View Post
    It's not a vbseo problem, it is a cache problem. Although I can't reproduce it, it just happened again today on my site. Here's the scenario.

    I created an article.
    After it was published, a user posted to notify me of an error in it.
    I corrected the error.
    A bit later, another user posted about the error (which I thought was strange since I fixed it).
    When I looked at the article, the error was not there.
    When I looked as unregistered, the error was there and the article only showed 1 comment (had 6 at that point).

    So for some reason, it seems like some articles are not passing the cache rebuild process and effecting unregistered users. I'm not too saavy, but I can't find anything related to the cache and permissions in the code. I cleared the CMS Cache via admincp and everything was immediately corrected.
    That's a clue. Thanks. Can't think offhand why that would affect anything but it gives me a place to look.

    Leave a comment:


  • reefland
    replied
    It's not a vbseo problem, it is a cache problem. Although I can't reproduce it, it just happened again today on my site. Here's the scenario.

    I created an article.
    After it was published, a user posted to notify me of an error in it.
    I corrected the error.
    A bit later, another user posted about the error (which I thought was strange since I fixed it).
    When I looked at the article, the error was not there.
    When I looked as unregistered, the error was there and the article only showed 1 comment (had 6 at that point).

    So for some reason, it seems like some articles are not passing the cache rebuild process and effecting unregistered users. I'm not too saavy, but I can't find anything related to the cache and permissions in the code. I cleared the CMS Cache via admincp and everything was immediately corrected.

    Leave a comment:


  • Bram
    replied
    Will upgrade vBseo to the latest version and see if the problem is solved

    Leave a comment:


  • Bram
    replied
    Happens here without vbseo too. Running the latest vb version.

    Leave a comment:


  • reefland
    replied
    Thanks Edwin, will do. My response was only because of the policy of support when add-ons are installed.

    Leave a comment:

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