Closed (fixed)
Project:
Submitted By
Version:
6.x-1.1
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
20 Aug 2008 at 15:27 UTC
Updated:
5 Mar 2011 at 02:40 UTC
Jump to comment: Most recent file
Comments
Comment #1
nancydruThis should fix it.
Comment #2
nancydruCommitted.
Comment #3
bonobo commentedSeeing this issue on both the dev version (that has this patch applied) and using 6.x-1.0
Using CCK 6.x-2.0-rc10 and Token 6.x-1.11; Drupal core 6.6
Comment #4
nancydruThis is strange; it works fine for me. Could you tell me what pattern you have, please? Are you sure you don't accidentally have an older version that is being used somehow?
Comment #5
bonobo commentedYup, I'm using the dev version of the module, and, fwiw, I've cleared all the cache tables in the db and the browser cache on the off-chance that something had been cached that was affecting what I was seeing.
On node creation, the pattern does not get used.
For testing purposes, I kept the replacement pattern simple: [yyyy]
Also, I'm very open to the possibility that this is a PEBKAC -- but I have yet to discover the obvious thing I'm overlooking. This module appears admirably straightforward: install submitted_by and token, and then enter the replacement pattern for different content types. Is there a step I'm missing?
Comment #6
nancydruI'm baffled. Yes, this module is that simple.
Comment #7
Cologner875 commentedAfter updating to version 6.x-1.1, this issue is not fixed, the module does not remember the content of 'Submitted by...' text. Perhaps I should mention that it did remember the content using Version 1.0 :) It would be great if that could finally be solved.
I'm using the module with Drupal 6.9 and Token 6.x-1.11, my webbrowser is Firefox 3.05 if that is important.
Comment #8
nancydruCan you tell me what other modules you have - especially if any were added after version 1.0.
Comment #9
Cologner875 commentedi only updated Submitted By, the other modules did not change. here are the modules, that are also displayed in the content-type edit-settings:
- Filter by node type 6.x-1.2
- Scheduler 6.x-1.3
- Diff 6.x-2.0
- Composite Layout 6.x-1.0-beta6
- Content Construction Kit (CCK) 6.x-2.1
- Content Access 6.x-1.0
-Administration menu 6.x-1.3 is always on top of the admin pages
I hope this helps to replicate it.
Comment #10
sourabh.iitm commentedEven i am facing this problem with version drupal 6.9 & submitted by 6.x-1.1. Every time i am trying to edit the content type, Submitted by field is empty. So saving any changes restores default settings.
I didn't had any previous version of this module. I have installed 6.x-1.1 so there is no update involved.
Comment #11
fheinley commentedI had the same problem with drupal 6.9 & submitted by 6.x-1.1 - when I looked, the values were getting saved, but the node editing form wasn't reading them back in.
I have changed the submitted_by.module file, line 68 (function submitted_by_form_node_type_form_alter)
from: $type = isset($form['identity']['type']) ? $form['identity']['type']['#value'] : '';
to: $type = isset($form['#node_type']->type) ? $form['#node_type']->type : '';
This has fixed it for me. Not sure how correct this is, but its working for me.
Comment #12
nancydruThank you very much, Frank. I have committed this fix. I also took the opportunity to alter the fieldset title and expand the fieldset when a value exists.
It is very interesting: When I started looking at this, I chose "story" and it was indeed experiencing this problem. But the types that I had been using for testing were not. I wonder why some types had that value and some did not?
Comment #13
nancydruComment #14
sourabh.iitm commentedThanks a lot. Development version is working for me too.
Comment #15
nancydruThanks for the update.
Comment #16
Cologner875 commentedThanks for the bugfix! What about making the curent dev version a stable release? :)
It would perhaps only contain this bugfix, but it improves usability a lot, also for users, who do not read the issues (and therefore would not install the dev version).
Comment #17
nancydruI don't normally like to create new releases more than once a month, but I did anyway.