Where are URL translations stored

«

Previous topic

|

|

Next topic

»

Author	Message
Andrew Kelly	Sunday 23 April 2006 10:11:05 am Hi all, I think I just shot myself in the foot and I'm hoping somebody out there can help me recover. I can no longer log into the admin side of my site, and I think it's becuase I stupidly entered a bad URL translatation forwarding all /user/* requests to the default node. Where are these translations stored, and what's the easiest way to reverse them when one can't log in? Andy
Kristof Coomans	Sunday 23 April 2006 10:26:12 am Take a look in the ezurlalias db table. I think you can just remove the problematic entry there. independent eZ Publish developer and service provider \| http://blog.coomanskristof.be \| http://ezpedia.org
Gabriel Ambuehl	Sunday 23 April 2006 10:33:18 am Yes that works. I had to do that myself at one time ;) phpmyadmin was definitely useful ;) Visit http://triligon.org
Andrew Kelly	Monday 24 April 2006 12:58:53 am Thanks, you two. The reason I posted was because I couldn't find anything in the ezurlalias table when I looked. But I was looking from the command line and going in blind. On a devel box I played back a backup from well before the URL translation addition, but was still having the same problem. Puzzled me a lot. I was coming to the conclusion that translations were stored somewhere in the filesystem when it dawned on me that I hadn't cleared caches (Doh!). After clearing caches I was able to log in to the devel box, no problem. So, long story short: I fired up pgadmin on my production server, found the nasty entry and deleted it, cleared the urlalias cache (I'm sOOOO glad there's a separate call for that) and Schiiing, I was in. Thanks again, both of you. If I hadn't found the solution after all, your responses would have saved my bacon this morning. Very much appreciated. Andy

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 31 2025 01:24:58
Script start
Timing:	Jan 31 2025 01:24:58
Module start 'layout'
Timing:	Jan 31 2025 01:24:58
Module start 'content'
Timing:	Jan 31 2025 01:24:58
Module end 'content'
Timing:	Jan 31 2025 01:24:58
Script end

Main resources:

Total runtime	0.0271 sec
Peak memory usage	8,192.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0067	588.1328	151.2109
Module start 'layout'	0.0067	0.0044	739.3438	220.6875
Module start 'content'	0.0111	0.0143	960.0313	1,001.7734
Module end 'content'	0.0254	0.0017	1,961.8047	33.9922
Script end	0.0271		1,995.7969

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0030	11.1657	14	0.0002
Check MTime	0.0012	4.2940	14	0.0001
Mysql Total
Database connection	0.0009	3.4737	1	0.0009
Mysqli_queries	0.0022	8.2829	3	0.0007
Looping result	0.0000	0.0475	1	0.0000
Template Total	0.0012	4.3	1	0.0012
Template load	0.0009	3.2934	1	0.0009
Template processing	0.0003	1.0330	1	0.0003
Override
Cache load	0.0006	2.3747	1	0.0006
General
dbfile	0.0015	5.4607	8	0.0002
String conversion	0.0000	0.0255	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs