Default URI of deleted objects

Previous topic

General

Next topic

Author	Message
Russell Michell	Sunday 28 September 2008 3:36:48 pm Hi there folks, Am I the only one that thinks the default eZ behaviour for linking to deleted content-objects is a little odd? * Create an Article called "Test", then publish it. * In any other existing Article object, add a link via the online editor to the Article "Test" then publish it. * Rename "Test" - the link to it in the existing Article is updated. Fine, all good. * Move "Test" to another folder - the link to it in the existing Article, is updated. Fine, all good. * <b>But</b> Delete "Test" to the Trash - the link to it in the existing Article, is updated - but to the default SiteURL? Is it possible to change the default location that links to deleted objects point to, and leave them as-is so that when you run something like runcronjobs.php, the link results in "invalid" being returned so it can be flagged as something that site-admins/editors need to check and fix? Cheers, Russ Russell Michell, Wellington, New Zealand. We're building! http://www.theruss.com/blog/ I'm on Twitter: http://twitter.com/therussdotcom Believe nothing, consider everything.
Mark Marsiglio	Sunday 28 September 2008 6:57:51 pm Try changing your error.ini settings. The settings that I use most often are: [ErrorSettings] DefaultErrorHandler=rerun DefaultRedirectURL=/content/view/error/2 DefaultRerunURL=/content/view/error/2 ErrorHandler[20]=rerun RerunURL[20]=/content/view/error/2 This results in the url staying the same, and 404 headers being sent to the user. We set up a custom override on the error view to show the sitemap and a search field so that the user can find the page that they were looking for. However, it will come back as an invalid link when you run an external checker on it. The internal link checker will not pick this up because it does not check eznode urls. However, if you have pages linked using the regular format of url (i.e. /folder/subfolder/page_name) either in relative or absolute format, the link checker should pick up the problem. To avoid dead link problems when deleting pages that are connected via eznode:// links, we recommend to our content managers that they check the Reverse Relations that the page has (using the admin interface) before deleting a page to see what other pages link to it, or have it embedded. http://www.thinkcreative.com Turning Ideas Into Strategic Solutions
Russell Michell	Monday 29 September 2008 3:46:13 pm Hi there and thanks Mark, I take your point with regard to ensuring deleted items no longer have reverse-linked items, but do you find this method works for links that point to items that have just been placed in the trash? What I mean is, once you access a page which used to link to a content-object but has just been removed to the trash, all URIs pointing to it seem to be auto-updated to what appears to be SiteURL from site.ini. How do you reconfigure eZ to change this URI? In override/error.ini.append.php if I use: [ErrorSettings] DefaultErrorHandler=displayerror If I now punch in a non-existent URL - I get the eZ default "Module Not Found" error (Error 20). But if I select the link that used to point to a normal content object (An Article for instance) but has since been moved to the trash, the link itself becomes updated - no eZ error, the link simply changes and becomes SiteURL. The same if I use your solution for override/error.ini.append.php DefaultErrorHandler=rerun DefaultRedirectURL=/content/view/987 DefaultRerunURL=/content/view/987 ErrorHandler[20]=rerun RerunURL[20]=/content/view/987 Or am I totally misunderstanding something (It wouldn't be the first time!) Cheers, Russ Russell Michell, Wellington, New Zealand. We're building! http://www.theruss.com/blog/ I'm on Twitter: http://twitter.com/therussdotcom Believe nothing, consider everything.

Author

Message

Russell Michell

Sunday 28 September 2008 3:36:48 pm

Hi there folks,

Am I the only one that thinks the default eZ behaviour for linking to deleted content-objects is a little odd?

* Create an Article called "Test", then publish it.
* In any other existing Article object, add a link via the online editor to the Article "Test" then publish it.
* Rename "Test" - the link to it in the existing Article is updated. Fine, all good.
* Move "Test" to another folder - the link to it in the existing Article, is updated. Fine, all good.
* <b>But</b> Delete "Test" to the Trash - the link to it in the existing Article, is updated - but to the default SiteURL?

Is it possible to change the default location that links to deleted objects point to, and leave them as-is so that when you run something like runcronjobs.php, the link results in "invalid" being returned so it can be flagged as something that site-admins/editors need to check and fix?

Cheers,
Russ

Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom

Believe nothing, consider everything.

Mark Marsiglio

Sunday 28 September 2008 6:57:51 pm

Try changing your error.ini settings. The settings that I use most often are:

[ErrorSettings]
DefaultErrorHandler=rerun
DefaultRedirectURL=/content/view/error/2
DefaultRerunURL=/content/view/error/2

ErrorHandler[20]=rerun
RerunURL[20]=/content/view/error/2

This results in the url staying the same, and 404 headers being sent to the user. We set up a custom override on the error view to show the sitemap and a search field so that the user can find the page that they were looking for. However, it will come back as an invalid link when you run an external checker on it.

The internal link checker will not pick this up because it does not check eznode urls. However, if you have pages linked using the regular format of url (i.e. /folder/subfolder/page_name) either in relative or absolute format, the link checker should pick up the problem.

To avoid dead link problems when deleting pages that are connected via eznode:// links, we recommend to our content managers that they check the Reverse Relations that the page has (using the admin interface) before deleting a page to see what other pages link to it, or have it embedded.

http://www.thinkcreative.com
Turning Ideas Into Strategic Solutions

Russell Michell

Monday 29 September 2008 3:46:13 pm

Hi there and thanks Mark,

I take your point with regard to ensuring deleted items no longer have reverse-linked items, but do you find this method works for links that point to items that have just been placed in the trash?

What I mean is, once you access a page which used to link to a content-object but has just been removed to the trash, all URIs pointing to it seem to be auto-updated to what appears to be SiteURL from site.ini. How do you reconfigure eZ to change this URI?

In override/error.ini.append.php if I use:

[ErrorSettings]
DefaultErrorHandler=displayerror

If I now punch in a non-existent URL - I get the eZ default "Module Not Found" error (Error 20). But if I select the link that used to point to a normal content object (An Article for instance) but has since been moved to the trash, the link itself becomes updated - no eZ error, the link simply changes and becomes SiteURL.

The same if I use your solution for override/error.ini.append.php

DefaultErrorHandler=rerun
DefaultRedirectURL=/content/view/987
DefaultRerunURL=/content/view/987
ErrorHandler[20]=rerun
RerunURL[20]=/content/view/987

Or am I totally misunderstanding something (It wouldn't be the first time!)
Cheers,
Russ

Russell Michell, Wellington, New Zealand.
We're building! http://www.theruss.com/blog/
I'm on Twitter: http://twitter.com/therussdotcom

Believe nothing, consider everything.

eZ debug

Timing:	Jan 19 2025 06:27:42
Script start
Timing:	Jan 19 2025 06:27:42
Module start 'layout'
Timing:	Jan 19 2025 06:27:42
Module start 'content'
Timing:	Jan 19 2025 06:27:43
Module end 'content'
Timing:	Jan 19 2025 06:27:43
Script end

Main resources:

Total runtime	1.1217 sec
Peak memory usage	4,096.0000 KB
Database Queries	57

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0048	589.1484	152.6250
Module start 'layout'	0.0048	0.0028	741.7734	39.4453
Module start 'content'	0.0076	1.1128	781.2188	554.7344
Module end 'content'	1.1204	0.0013	1,335.9531	16.1641
Script end	1.1217		1,352.1172

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0031	0.2773	16	0.0002
Check MTime	0.0013	0.1195	16	0.0001
Mysql Total
Database connection	0.0007	0.0658	1	0.0007
Mysqli_queries	1.0709	95.4698	57	0.0188
Looping result	0.0005	0.0419	55	0.0000
Template Total	1.0927	97.4	2	0.5464
Template load	0.0021	0.1874	2	0.0011
Template processing	1.0906	97.2226	2	0.5453
Template load and register function	0.0001	0.0078	1	0.0001
states
state_id_array	0.0009	0.0784	1	0.0009
state_identifier_array	0.0010	0.0905	2	0.0005
Override
Cache load	0.0017	0.1523	34	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0004	0.0336	2	0.0002
Fetch class attribute name	0.0009	0.0827	5	0.0002
XML
Image XML parsing	0.0009	0.0772	2	0.0004
class_abstraction
Instantiating content class attribute	0.0000	0.0009	6	0.0000
General
dbfile	0.0009	0.0816	21	0.0000
String conversion	0.0000	0.0006	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
3	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
3	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
8	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
3	content/datatype/view/ezxmltags/literal.tpl	<No override>	extension/community/design/standard/templates/content/datatype/view/ezxmltags/literal.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 22 Number of unique templates used: 7

Time used to render debug report: 0.0001 secs