Last post 7 hours 36 min ago

Posts last week 82

Average response time last week 34 min

All time posts 68071

All time tickets 10515

All time avg. posts per day 20

Helpdesk is open from Monday through Friday CET

Please create an (free) account to post any question in the support area.

Please check the development versions area. Look at the changelog, maybe your specific problem has been resolved already!

All tickets are private and they cannot be viewed by anyone. We have made public only a few tickets that we found helpful, after removing private information from them.

#4336 – Consequences of purging all records

Posted in ‘sh404SEF’

This is a public ticket. Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Monday, 20 November 2017 16:11 UTC

HeadGofer

Hi,

Just following up on ticket 4326.

The site seems sluggish today. I initially removed caching and have now reinstated it. Seems to help. However, I'm concerned with the comment you made about things being out of sync with the database. Therefore I'm wondering what would be the consequences of purging the records and starting over.

Let me know when you can.

Monday, 20 November 2017 17:07 UTC

wb_weeblr

Hi

Like I said then, there is no problem in having the cached enabled, as long as you do not play with data directly in the database. If you delete/modify things in the database, then sh404SEF is not informed and the cache will have different URL records than the database. Those modified items in the database maybe not be taken into account for instance.

As for Purging, this will delete all URL records in the database. That's not recommended on a live site, as all URLs will have to be recreated. This will generate an additional load, as crating the SEF URLs is by far the most resource intensive task. Once the URLs are in the DB, they can be read easily and quickly.
Also, URLs are only recreated when Joomla asks us to do to, for instance because Joomla needs a URL to be displayed on a page. Thus, after Purging, URLs will trigger a 404 until at least one visitors asks to visit a page where a link to that URL exists. This may create 404s for users coming directly from search engines or bookmarked links.

RGds

Monday, 20 November 2017 17:21 UTC

HeadGofer

Thank you for your response.

Unfortunately, I wasn't aware of the URL Cache situation and did delete records with it on. However, those records were of JEvents dating back to 2003 and since those events are long passed, I'm not sure of the likelihood of people searching for them or clicking on them.

What are the consequences of disabling and then reenabling the disk cache? Does it reset?

Finally, when you say the correspondences between the db and the cache get confused is that only for the deleted records or does it effect all the records?

Monday, 20 November 2017 17:27 UTC

wb_weeblr

What are the consequences of disabling and then reenabling the disk cache? Does it reset?

No it won't reset. To do that, another very simple way is to go to the /components/com_sh404SEF/cache folder and manually delete anything but the index.html file

Finally, when you say the correspondences between the db and the cache get confused is that only for the deleted records or does it effect all the records?

Entirely dependson what you did directly to the DB without updating the cache. If you deleted something, it might be still in the cache. If you added something to the DB however, there is no problem as this is a normal situation: when the cache is a miss, then we read the DB to try find the URL.

Rgds

Monday, 20 November 2017 18:00 UTC

HeadGofer

Sorry to be so uninformed. What are the consequences of restarting the disc cache?

On Mon, Nov 20, 2017 at 12:27 PM, Weeblr <[email protected]> wrote:

Monday, 20 November 2017 19:05 UTC

wb_weeblr

Sorry to be so uninformed. What are the consequences of restarting the disc cache?

None unless, again, you deleted some URLs in the database, but they are still in the cache file. If you deleted from the database any URL that can be in the cache file, you need to manually delete the cache file, as explained above, or else sh404SEF will still "see" the copy in the cache.

Rgds

Monday, 20 November 2017 20:55 UTC

HeadGofer

Thanks for the clarification. I think we can close the ticket.

Tuesday, 21 November 2017 08:09 UTC

wb_weeblr

Hi

Closing this ticket now, feel free to open a new one as needed. If you do so, please mention this ticket number in the new one.

If you created any superadmin account for us, be sure to delete or block it now to avoid unnecessary risk in the future.

Be sure to also check out wbAMP, our new Accelerated Mobiles pages plugin for Joomla - the next big thing is SEO, direct from Google themselves!

Rgds

This ticket is closed, therefore read-only. You can no longer reply to it. If you need to provide more information, please open a new ticket and mention this ticket's number.