Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • ceeyee Friend
    #731025

    The new articles won’t show up in JA News Featured unless we clear site wide cache.
    This is clearly a bug. However, the ticket was marked as “Won’t solve because it’s not a bug” after I have waited for a year!

    This is a major bug for this template, a news site template. How can a news website not able to reflect recent news?

    The bug report may appear as a development suggestion, but it’s not. Please look at the first half of the original post and you can see it’s a bug report.

    http://pm.joomlart.com/browse/JAECPLGTIIIJOOMLAIVI-617
    Also reported here
    http://id.joomlart.com/forums/topic/new-articles-not-showing-up-on-ja-news-featured/

    Please fix this bug. It’s very important for this template.

    Thank you.

    jooservices Friend
    #749681

    Hi there
    As far i can understand your issue.

    # Your site have enabled cached via Joomla! Global configuration.
    # You are using JA News Featured on your site.
    # You have add / update articles in backend. But it’s not update at frontpage until clear cache or cache expired ( and purged to get new cache )

    Isn’t it ?

    Thank you,
    Viet Vu

    ceeyee Friend
    #749682

    <em>@jooservices 494081 wrote:</em><blockquote>Hi there
    As far i can understand your issue.

    # Your site have enabled cached via Joomla! Global configuration.
    # You are using JA News Featured on your site.
    # You have add / update articles in backend. But it’s not update at frontpage until clear cache or cache expired ( and purged to get new cache )

    Isn’t it ?

    Thank you,
    Viet Vu</blockquote>

    Yes, though the Cache I am using JA cache. Let me double check when I get back to the office.
    Thank you.

    jooservices Friend
    #749683

    Hi there
    In this case it’s not a bug . Confirmed . Reason is

    – You are using cached. It’s a way to reduce server process in heavy by store executed data into cache. In next time page load, it’ll load data from these cache instead execute whole processing .
    On your site

    – First time site load, everything will process : query into database to get data, execute data and respond html to render into your browser. These data will be cached into server cache ( in normally it’s file caches, located under JPATH_ROOT/cache ).
    And of course module JA News Featured is part of these.
    – Second time site load, if cache still exists and is not expired. Instead query again into database to get data, it’ll load from cached.
    And of course, if you have any changed data between first time & second time it’s stored in database BUT no database queried than of course it’s not update in render.

    In this cache you’ll reduce server process to improve performance.
    For sample: If you have 1.000 request at same time. Without caching, your server will need query into database, process it in 1.000 times. !!! Really heavy for server.

    But if in your concept you want to keep everything update. There are few ways you can do
    – Turn of Joomla! Cache. Nothing will be cache but you’ll pay for performance of site
    – Exclude extension ( in this case is Module JA News Features ) out of caching. You can check it in module configuration. By this way this module will always update directly from database and process instead load from cached.
    – Manual ( or automate ) clear site cache after any changed.

    Thank you,
    Viet Vu

    ceeyee Friend
    #749953

    <em>@jooservices 494083 wrote:</em><blockquote>Hi there
    In this case it’s not a bug . Confirmed . Reason is

    – You are using cached. It’s a way to reduce server process in heavy by store executed data into cache. In next time page load, it’ll load data from these cache instead execute whole processing .
    On your site

    – First time site load, everything will process : query into database to get data, execute data and respond html to render into your browser. These data will be cached into server cache ( in normally it’s file caches, located under JPATH_ROOT/cache ).
    And of course module JA News Featured is part of these.
    – Second time site load, if cache still exists and is not expired. Instead query again into database to get data, it’ll load from cached.
    And of course, if you have any changed data between first time & second time it’s stored in database BUT no database queried than of course it’s not update in render.

    In this cache you’ll reduce server process to improve performance.
    For sample: If you have 1.000 request at same time. Without caching, your server will need query into database, process it in 1.000 times. !!! Really heavy for server.

    But if in your concept you want to keep everything update. There are few ways you can do
    – Turn of Joomla! Cache. Nothing will be cache but you’ll pay for performance of site
    – Exclude extension ( in this case is Module JA News Features ) out of caching. You can check it in module configuration. By this way this module will always update directly from database and process instead load from cached.
    – Manual ( or automate ) clear site cache after any changed.

    Thank you,
    Viet Vu</blockquote>

    Option 2 is the only viable solution, but we failed to implement it.
    Our site admins have tried adding “mod=mod_janews_featured,mod_newspro” into Cache Exclude, but it didn’t solve the problem.
    We also tried adding “component=com_content” and that didn’t work either.

    New articles still won’t update on JA News Featured unless I clear site-wide JAT3 cache.

    jooservices Friend
    #749973

    Hi there
    There are 2 thing we need to know in this issue.

    # We have confirmed it’s bug. It’s Joomla! concept and how does web work with cache.
    # And in second we need to know how to clear Joomla! cache or exclude for some elements.

    As i said. It’s Joomla! cache not T3 cache ! But in your screenshot you have mentioned about T3 cache.
    Please check into module configuration, there are often have Enable cache params .

    https://docs.joomla.org/Cache

    But if it doesn’t you stil can do ( just by follow logic : Exclude this cache )
    – Use cron to delete cache directories / files

    https://www.maketecheasier.com/delete-old-files-in-a-folder-automatically-in-linux/
    – Or really basic way. Turn off all cache. Because you have focused on update instead performance than we just turn off cache.

    Thank you,
    Viet Vu

Viewing 6 posts - 1 through 6 (of 6 total)

This topic contains 6 replies, has 2 voices, and was last updated by  jooservices 8 years, 7 months ago.

We moved to new unified forum. Please post all new support queries in our New Forum