Mailing List Archive: Bricolage: devel

interface UI / state errors in 1.11.1 and svn trunk

Index | Next | Previous | View Threaded

john.durkin at gmail

Nov 21, 2008, 9:57 AM

Post #1 of 8 (2241 views)
Permalink

interface UI / state errors in 1.11.1 and svn trunk

I was waiting until I upgraded to svn trunk to be sure these errors
persist. I upgraded last night and tested it out, and I am still having
these problems.

1. Create New Media & Add Contributor error:

- If you create a new media using "or upload as" from inside a story by
clicking the edit button of a related media element, and you wish to add a
contributor to that media item, you click "add" and the window closes.
- Back in the story, if you hit save and stay, your story refreshes and
*does* have the media related, which is nice :).
- Still - it will cut out many steps for the editor if he can just add
the contributor to the media file at upload / creation time from within a
story.

2. Adding new elements to stories, WYSIWYG fields, state errors:

- When you add a new element to a story that contains WYSIWYG fields,
those fields become textareas.
- Also, if the WYSIWYG fields are filled in with any data that was not
"save and stay"ed before adding the new element, that data is lost.
- After adding the new element, if you save and stay the story, the
textareas go back to being WYSIWYG fields again (minus any data entered
after the last "save"), but the story reports twice:

Warning! State inconsistent: Please use the buttons provided by the
application rather than the 'Back'/'Forward' buttons.
Warning! State inconsistent: Please use the buttons provided by the
application rather than the 'Back'/'Forward' buttons.

john.durkin at gmail

Nov 21, 2008, 10:05 AM

Post #2 of 8 (2140 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

Replying to my own email here to include one other odd thing - there doesn't
appear to be a way to reorder story elements from the UI anymore... and -
when you are trying to order the custom fields in the "create element" form
- it asks you the position before you add the element, but once added
(inside edit area on a custom field) there is no way to reorder.

On Fri, Nov 21, 2008 at 9:57 AM, John Durkin <john.durkin [at] gmail> wrote:

> I was waiting until I upgraded to svn trunk to be sure these errors
> persist. I upgraded last night and tested it out, and I am still having
> these problems.
>
> 1. Create New Media & Add Contributor error:
>
> - If you create a new media using "or upload as" from inside a story by
> clicking the edit button of a related media element, and you wish to add a
> contributor to that media item, you click "add" and the window closes.
> - Back in the story, if you hit save and stay, your story refreshes and
> *does* have the media related, which is nice :).
> - Still - it will cut out many steps for the editor if he can just add
> the contributor to the media file at upload / creation time from within a
> story.
>
> 2. Adding new elements to stories, WYSIWYG fields, state errors:
>
> - When you add a new element to a story that contains WYSIWYG fields,
> those fields become textareas.
> - Also, if the WYSIWYG fields are filled in with any data that was not
> "save and stay"ed before adding the new element, that data is lost.
> - After adding the new element, if you save and stay the story, the
> textareas go back to being WYSIWYG fields again (minus any data entered
> after the last "save"), but the story reports twice:
>
> Warning! State inconsistent: Please use the buttons provided by the
> application rather than the 'Back'/'Forward' buttons.
> Warning! State inconsistent: Please use the buttons provided by the
> application rather than the 'Back'/'Forward' buttons.
>
>
>
>
>
>
>

david at kineticode

Nov 21, 2008, 2:48 PM

Post #3 of 8 (2131 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

On Nov 21, 2008, at 9:57 AM, John Durkin wrote:

> 1. Create New Media & Add Contributor error:
>
> - If you create a new media using "or upload as" from inside a
> story by
> clicking the edit button of a related media element, and you wish
> to add a
> contributor to that media item, you click "add" and the window
> closes.

Please file a bug report.

> - Back in the story, if you hit save and stay, your story
> refreshes and
> *does* have the media related, which is nice :).
> - Still - it will cut out many steps for the editor if he can just
> add
> the contributor to the media file at upload / creation time from
> within a
> story.

Of course. It's a bug.

> 2. Adding new elements to stories, WYSIWYG fields, state errors:
>
> - When you add a new element to a story that contains WYSIWYG
> fields,
> those fields become textareas.

Another bug.

> - Also, if the WYSIWYG fields are filled in with any data that was
> not
> "save and stay"ed before adding the new element, that data is lost.

I don't follow.

> - After adding the new element, if you save and stay the story, the
> textareas go back to being WYSIWYG fields again (minus any data
> entered
> after the last "save"), but the story reports twice:
>
> Warning! State inconsistent: Please use the buttons provided by the
> application rather than the 'Back'/'Forward' buttons.
> Warning! State inconsistent: Please use the buttons provided by the
> application rather than the 'Back'/'Forward' buttons.

Huh. Yeah, that's another bug.

Thanks,

David

john.durkin at gmail

Nov 21, 2008, 2:50 PM

Post #4 of 8 (2140 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

ok bug reports forthcoming :)

On Fri, Nov 21, 2008 at 2:48 PM, David E. Wheeler <david [at] kineticode>wrote:

> On Nov 21, 2008, at 9:57 AM, John Durkin wrote:
>
> 1. Create New Media & Add Contributor error:
>>
>> - If you create a new media using "or upload as" from inside a story by
>> clicking the edit button of a related media element, and you wish to add
>> a
>> contributor to that media item, you click "add" and the window closes.
>>
>
> Please file a bug report.
>
> - Back in the story, if you hit save and stay, your story refreshes and
>> *does* have the media related, which is nice :).
>> - Still - it will cut out many steps for the editor if he can just add
>> the contributor to the media file at upload / creation time from within a
>> story.
>>
>
> Of course. It's a bug.
>
> 2. Adding new elements to stories, WYSIWYG fields, state errors:
>>
>> - When you add a new element to a story that contains WYSIWYG fields,
>> those fields become textareas.
>>
>
> Another bug.
>
> - Also, if the WYSIWYG fields are filled in with any data that was not
>> "save and stay"ed before adding the new element, that data is lost.
>>
>
> I don't follow.
>
> - After adding the new element, if you save and stay the story, the
>> textareas go back to being WYSIWYG fields again (minus any data entered
>> after the last "save"), but the story reports twice:
>>
>> Warning! State inconsistent: Please use the buttons provided by the
>> application rather than the 'Back'/'Forward' buttons.
>> Warning! State inconsistent: Please use the buttons provided by the
>> application rather than the 'Back'/'Forward' buttons.
>>
>
> Huh. Yeah, that's another bug.
>
> Thanks,
>
> David
>

rolfm at denison

Nov 21, 2008, 4:10 PM

Post #5 of 8 (2129 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

On Nov 21, 2008, at 12:57 PM, John Durkin wrote:

> Warning! State inconsistent: Please use the buttons provided by the
> application rather than the 'Back'/'Forward' buttons.
> Warning! State inconsistent: Please use the buttons provided by the
> application rather than the 'Back'/'Forward' buttons.

Just out of curiousity, what browser were you using?

-Matt

john.durkin at gmail

Nov 21, 2008, 4:30 PM

Post #6 of 8 (2141 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

Hey Matt,

I'm using firefox 3.0.4. I can't use Safari because I have not been able to
fix the WYSIWYGs - they show up collapsed in Safari. I will test this in
another browser or two before submitting bug reports for more info... The
WYSIWYG I'm using is Xinha.

On Fri, Nov 21, 2008 at 4:10 PM, Matt Rolf <rolfm [at] denison> wrote:

>
> On Nov 21, 2008, at 12:57 PM, John Durkin wrote:
>
> Warning! State inconsistent: Please use the buttons provided by the
>> application rather than the 'Back'/'Forward' buttons.
>> Warning! State inconsistent: Please use the buttons provided by the
>> application rather than the 'Back'/'Forward' buttons.
>>
>
> Just out of curiousity, what browser were you using?
>
> -Matt
>

john.durkin at gmail

Nov 21, 2008, 4:37 PM

Post #7 of 8 (2132 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

Checked in Safari - and actually - the WYSIWYGs do not show up collapsed
anymore. Yah! The other errors persist though, except I don't get the
inconsistent state error twice in safari, just once.

JD

On Fri, Nov 21, 2008 at 4:30 PM, John Durkin <john.durkin [at] gmail> wrote:

> Hey Matt,
>
> I'm using firefox 3.0.4. I can't use Safari because I have not been able
> to fix the WYSIWYGs - they show up collapsed in Safari. I will test this in
> another browser or two before submitting bug reports for more info... The
> WYSIWYG I'm using is Xinha.
>
>
> On Fri, Nov 21, 2008 at 4:10 PM, Matt Rolf <rolfm [at] denison> wrote:
>
>>
>> On Nov 21, 2008, at 12:57 PM, John Durkin wrote:
>>
>> Warning! State inconsistent: Please use the buttons provided by the
>>> application rather than the 'Back'/'Forward' buttons.
>>> Warning! State inconsistent: Please use the buttons provided by the
>>> application rather than the 'Back'/'Forward' buttons.
>>>
>>
>> Just out of curiousity, what browser were you using?
>>
>> -Matt
>>
>
>

rolfm at denison

Feb 26, 2009, 7:51 AM

Post #8 of 8 (1555 views)
Permalink

Re: interface UI / state errors in 1.11.1 and svn trunk [In reply to]

Did the bugs in this thread ever get reported?

-Matt

On Nov 21, 2008, at 5:50 PM, John Durkin wrote:

> ok bug reports forthcoming :)
>
> On Fri, Nov 21, 2008 at 2:48 PM, David E. Wheeler <david [at] kineticode
> >wrote:
>
>> On Nov 21, 2008, at 9:57 AM, John Durkin wrote:
>>
>> 1. Create New Media & Add Contributor error:
>>>
>>> - If you create a new media using "or upload as" from inside a
>>> story by
>>> clicking the edit button of a related media element, and you wish
>>> to add
>>> a
>>> contributor to that media item, you click "add" and the window
>>> closes.
>>>
>>
>> Please file a bug report.
>>
>> - Back in the story, if you hit save and stay, your story
>> refreshes and
>>> *does* have the media related, which is nice :).
>>> - Still - it will cut out many steps for the editor if he can just
>>> add
>>> the contributor to the media file at upload / creation time from
>>> within a
>>> story.
>>>
>>
>> Of course. It's a bug.
>>
>> 2. Adding new elements to stories, WYSIWYG fields, state errors:
>>>
>>> - When you add a new element to a story that contains WYSIWYG
>>> fields,
>>> those fields become textareas.
>>>
>>
>> Another bug.
>>
>> - Also, if the WYSIWYG fields are filled in with any data that was
>> not
>>> "save and stay"ed before adding the new element, that data is lost.
>>>
>>
>> I don't follow.
>>
>> - After adding the new element, if you save and stay the story, the
>>> textareas go back to being WYSIWYG fields again (minus any data
>>> entered
>>> after the last "save"), but the story reports twice:
>>>
>>> Warning! State inconsistent: Please use the buttons provided by the
>>> application rather than the 'Back'/'Forward' buttons.
>>> Warning! State inconsistent: Please use the buttons provided by the
>>> application rather than the 'Back'/'Forward' buttons.
>>>
>>
>> Huh. Yeah, that's another bug.
>>
>> Thanks,
>>
>> David
>>

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact Gossamer Threads