#142 — Title of weblog entry cannot be a whole number
by
Jan Hackel
—
last modified
Jul 06, 2010 03:36 PM
| State | Confirmed |
|---|---|
| Version: | 1.7 |
| Area | Functionality |
| Issue type | Bug |
| Severity | Low |
| Submitted by | Jan Hackel |
| Submitted on | Sep 12, 2008 |
| Responsible |
—
|
| Target release: | 2.0 |
Entering a number as the title of a blog entry will make Quills interpret the entry id as an archive URL.
- Steps to reproduce:
- Create a new weblog entry through the web. As title enter "10", for instance. Now save the entry.
You now get an error page telling that the requested page does not exist. This is because it tries to get a weblogentry_view for an archive of year 10. Furthermore you cannot navigate to the entry via it's id. This will show the archive of year 10.
Added by
Jan Hackel
on
Sep 12, 2008 07:52 PM
There is now a test-case in svn trunk of Product.Quills demonstrating the issue (rev. 71707).
Target release:
1.7
→
None
Responsible manager:
jhackel
→
(UNASSIGNED)
Added by
Jan Hackel
on
Nov 25, 2008 08:38 PM
Starting to fix...
Issue state:
unconfirmed
→
open
Target release:
None
→
1.7
Responsible manager:
(UNASSIGNED)
→
jhackel
Added by
Jan Hackel
on
Nov 25, 2008 08:41 PM
Issue state:
open
→
in-progress
Added by
Jan Hackel
on
Feb 26, 2009 10:52 AM
Severity:
Medium
→
Low
Added by
Jan Hackel
on
May 17, 2009 08:54 PM
Postponing until somewhere before release 2.0. This cannot easily be fixed as it is a issue by design. Any virtual URL Quills uses causes this problem, i.e. authors and topics too. IMO the proper solution would be to define a priority of view, e.g. the archive view always overrides the post view. The blog would emit a warning once the a user *reads* an ambiguous object (e.g. in the archive view shown) which contains a link to the hidden object (the post).
Issue state:
In progress
→
Postponed
Responsible manager:
jhackel
→
(UNASSIGNED)
Target release:
1.7
→
2.0
Added by
Jan Hackel
on
May 17, 2009 09:00 PM
I just realized that "postponed" means sort of "dumped" so I am reopening that issue again.
Issue state:
Postponed
→
Confirmed
Added by
Lucie Lejard
on
Jul 06, 2010 03:36 PM
As of July 6h 2010, I confirm this issue is still happening.
No responses can be added.
If you can, please log in before submitting a reaction.
