Ticket #437 (closed defect: wontfix)
Error with summary field
| Reported by: | ed | Owned by: | ed |
|---|---|---|---|
| Priority: | critical | Milestone: | PSE |
| Component: | Drupal modules & settings | Keywords: | |
| Cc: | Estimated Number of Hours: | 0.0 | |
| Add Hours to Ticket: | 0 | Billable?: | yes |
| Total Hours: | 0 |
Description
User gets this when trying to update profile: Looks like something is spilling out of the projects summary form - adding to PSE as it's connected...
JulianBriggs? (https://www.transitionnetwork.org/users/julianbriggs) sent a
message using the contact form at https://www.transitionnetwork.org/contact.
Just updated my profile and got this:
You specified that the summary should not be shown when this post is
displayed in full view. This setting has been ignored since you have not
defined a summary for the post. (To define a summary, insert the delimiter
"" (without the quotes) in the Body of the post to indicate the
end of the summary and the start of the main content.)
You specified that the summary should not be shown when this post is
displayed in full view. This setting has been ignored since you have not
defined a summary for the post. (To define a summary, insert the delimiter
"" (without the quotes) in the Body of the post to indicate the
end of the summary and the start of the main content.)
As a newby this means little. I just wanted to update my profile.
thanks
Julian
No connection to PSE whatsoever... You had me worried for a moment!
Julian had unchecked the "[x] Show summary in full view" checkbox just above the WYSIWYG editor and got a warning the summary (teaser) does not exist because he hadn't put in a teaser break. Hmmm...
This is an issue with the WYSIWYG module, see: http://drupal.org/node/575176 <-- it might be nice to look at patches here, but then again it might just be better to wait for the next release of said module.
---
FYI I've checked my PSE code and put checks in place that mean my module only functions where the URL is /pse/widget/* or /pse/widget/* etc... Additionally, nothing will work in PSE without a valid user and initiative ID, plus no hooks will run without these checks being made first.
Examples of checks in code:
To my knowledge there's no PSE code that does anything scary that doesn't need the above checks. I'll do another audit before we go to Beta.
Update this ticket if this issue is important enough that it needs a patch from the first link.