bugs at lists
Mar 11, 2009, 9:14 AM
Post #1 of 1
(516 views)
Permalink
|
|
[Bug 1446] New: stories not publishing to current primary_uri when changing slugs
|
|
http://bugs.bricolage.cc/show_bug.cgi?id=1446
Summary: stories not publishing to current primary_uri when
changing slugs
Product: Bricolage
Version: 1.10.6 - Current stable release
Platform: All
OS/Version: All
Status: NEW
Severity: normal
Priority: P3
Component: Unknown
AssignedTo: bugs [at] lists
ReportedBy: acaul [at] rand
I am repairing a story that was created with a space in its slug (which had
resulted in a space in the file name).
1.) When I correct the slug, save-and-stay, and then check-in-and-publish, the
old file does not get deleted and then replaced by the new file name.
2.) I changed the slug back to have a space in it and then added an expire
date. When I check-in and_publish, it removes the spaced file name from the
server.
3.) I checked the story back out, re-corrected the slug (to have no space),
removed the expire date. When I check-in-and-publish, it publishes to the
server, but outputs the file with the old file name, i.e. the file name with
the space in it.
4.) I looked through Postgres.
story and story_instance have the uri/slug with no space.
story_uri has a uri with no space
resource has a uri and path with a space. the value in the mod_time
field is the original create date of the story.
There were some other stories with the space-in-the-slug problem. Some
of those were repaired without issue. In resource, those have an entry with the
space in the uri and path fields and a mod_time from the create date. These
ALSO have a record with the corrected (no space) uri and path and a mod_time of
right now. This suggests that something is interfering with the corrected
information being written to the 'resource' table.
--
Configure bugmail: http://bugs.bricolage.cc/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching all bug changes.
|
