Closed
Bug 452141
Opened 16 years ago
Closed 15 years ago
Input format issues when editing existing posts
Categories
(Websites Graveyard :: spreadfirefox.com, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
3.0
People
(Reporter: alix, Unassigned)
References
()
Details
Attachments
(1 file)
549.98 KB,
image/png
|
Details |
When trying to edit the body of a group or a post (as a vanguard user), I get the following error: "You must use the default input format when authoring a group node." The only thing that seems to fix it is when I select plain text as the input format, which won't work for posts that need to be in full html.
Comment 1•16 years ago
|
||
This problem can be resolved by changing the default input format to filtered html @ admin/settings/filters More information here .. http://drupal.org/node/243963
Comment 2•16 years ago
|
||
Closing this ticket as there has been now further follow up in the last month. Please reopen if you need any further assistance. Best, Paul
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Apologies if I have the wrong bug, but there are some issues with the group page -- no WYSIWYG editor. You have to edit the HTML source code after you create a group. This is the same thing with the adding an event and adding a comment. This really makes it hard for users to create a cool group page and keep it relevant. It also appears that group pages don't offer full HTML so we can embed video etc. Jay can provide more details.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 4•16 years ago
|
||
I looked into the input types and OG settings and content types and can't figure out why this isn't work as it should. There are 2 issues that might be related. First, I don't see the wysiwyg editor after creating a group (the editor is there when creating a new group). So after the group is created, you can no longer edit the group page/node easily (must work in plaintext mode and edit the HTML markup)... which SUCKS! The other thing is that you can't change the input type for a group node after you created it. Even if I wanted to deal with HTML markup, I can't use all the tags I want because I can't change the setting to Full HTML... which also SUCKS! So trying to edit a group page after creation is pretty much useless. We really really need to get this fixed, since SFX is completely driven by OG and folks are creating groups all the time.
Comment 5•16 years ago
|
||
Hi Jay I'll have a look at both of these problems on stage as soon as the login problem is fixed they shouldn't be too difficult to resolve. Best, Paul
Comment 7•16 years ago
|
||
There are some problems to be resolved If you go to .. http://spreadfirefox.authstage.mozilla.com/ your redirected to .. https://spreadfirefox.authstage.mozilla.com/ if you then login then your redirected to .. http://spreadfirefox.stage.mozilla.com/node but shown as logged out but if you then manually go to .. http://spreadfirefox.authstage.mozilla.com/ your again redirected to .. https://spreadfirefox.authstage.mozilla.com/ and are logged in. We just need to stay in the realm of http://spreadfirefox.authstage.mozilla.com/ Paul
Comment 8•16 years ago
|
||
bug(In reply to comment #7) > There are some problems to be resolved yes, bug 477870 is to fix these, thanks.
Comment 9•16 years ago
|
||
the stage log in problems have been fixed
Comment 10•16 years ago
|
||
You can't see me, but I am dancing here :)
Updated•16 years ago
|
Assignee: nobody → paul
Comment 11•15 years ago
|
||
There is no FCKeditor appearing on stage at all presently although it looks to be configured correctly. Also after creating a group when i go back and try to alter the "input format" option there are no options available. Not sure what has happened here. On my local server running a vanilla D5 install with the latest version of OG / FCK there are no problems in relation to FCK editor / Input formats . Can we get the latest versions of these modules on stage? i think then any residual problems will be theme related.
Comment 12•15 years ago
|
||
All of the problems mentioned here look to now be resolved on stage. Paul
Comment 13•15 years ago
|
||
Resolving this bug as fixed. Please let me know if you need any further assistance. Best, Paul
Status: REOPENED → RESOLVED
Closed: 16 years ago → 15 years ago
Resolution: --- → FIXED
Comment 14•15 years ago
|
||
Hey there: Not sure this is resolved yet :) Let's all try this and have QA validate it. Alex: Did you do something to resolve it? And, if so, can we make sure it is pushed live when we relaunch the site?
Seems to be working fine now for me; Krupa?
Updated•15 years ago
|
Assignee: paul → nobody
Comment 16•15 years ago
|
||
works for me too.
Comment 18•15 years ago
|
||
Yay!
Assignee | ||
Updated•13 years ago
|
Product: Websites → Websites Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•