Keywords cleanup or regeneration

« 
Previous topic
|
Developer
|
Next topic
 »
Author Message

Piotrek Karaś

Saturday 15 December 2007 12:44:06 pm

Hello folks,

Is there actually such script available for keyword attribute's data?

I've just removed a substantial portion of content from my site (with keyword attributes) and was surprised not to see any change to the tag cloud that is based on keyword attributes. So went directly to script directories, but found nothing, either...

How does this actually work? Is there any mechanism for updates ready yet?
Or is it intentional to build up keyword inventory?

If there's nothing out there, I'll submit an enhancement proposal.

<i>PS. Seems like a shopping weekend before Christmas... ;) Very quiet around ;)</i>

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Piotrek Karaś

Saturday 15 December 2007 1:42:20 pm

Well, my bad! Keywords are taken care of when managing content... I must have mixed something up, which also led me to wrong conclusions about how the work internally.

--
Company: mediaSELF Sp. z o.o., http://www.mediaself.pl
eZ references: http://ez.no/partners/worldwide_partners/mediaself
eZ certified developer: http://ez.no/certification/verify/272585
eZ blog: http://ez.ryba.eu

Andy Caiger

Friday 02 July 2010 4:52:04 am

I'd like to know if there's a way to regenerate the tag cloud. On our website we've noticed that the counts on the tag cloud page are very wrong, even though they are correct on the individual keywords pages.

EAB - Integrated Internet Success
Offices in England, France & China.
http://www.eab.co.uk http://www.eab-china.com http://www.eab-france.com
Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing: Jan 18 2025 19:35:44
Script start
Timing: Jan 18 2025 19:35:44
Module start 'layout'
Timing: Jan 18 2025 19:35:44
Module start 'content'
Timing: Jan 18 2025 19:35:44
Module end 'content'
Timing: Jan 18 2025 19:35:44
Script end

Main resources:

Total runtime0.0143 sec
Peak memory usage2,048.0000 KB
Database Queries3

Timing points:

CheckpointStart (sec)Duration (sec)Memory at start (KB)Memory used (KB)
Script start 0.00000.0047 589.3516152.6250
Module start 'layout' 0.00470.0030 741.976639.4453
Module start 'content' 0.00780.0047 781.421993.3359
Module end 'content' 0.01250.0018 874.757834.3047
Script end 0.0143  909.0625 

Time accumulators:

 Accumulator Duration (sec) Duration (%) Count Average (sec)
Ini load
Load cache0.002316.3737140.0002
Check MTime0.00117.3998140.0001
Mysql Total
Database connection0.00074.697310.0007
Mysqli_queries0.002417.118230.0008
Looping result0.00000.197010.0000
Template Total0.001510.410.0015
Template load0.00085.503510.0008
Template processing0.00074.900910.0007
Override
Cache load0.00053.480410.0005
General
dbfile0.00021.580880.0000
String conversion0.00000.075140.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

UsageRequested templateTemplateTemplate loadedEditOverride
1print_pagelayout.tpl<No override>extension/community/design/community/templates/print_pagelayout.tplEdit templateOverride template
 Number of times templates used: 1
 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs