Nabble - LiveWorks!

Re: Session Problem

2008-09-03T01:07:56Z

Hi all,
Good suggestions in this thread, I'll try to pull them together into a
future LiveWorks! article. I can add a couple of suggestions.

On 03/09/2008 02:14, "John Vanantwerp" <JVanantwerp@...> wrote:
> We use option #1 in our installation, with the addition of an alert box
> as part of the timeout refresh. We have the alert box, which stops JS
> execution, appear about 10 minutes before the session expires. If the
> user hits OK on the alert box, the AJAXy code does a roundtrip to the
> server which refreshes the session timer. If they don't hit OK, the
> session times out as planned. So if they walk away the session expires,
> if they keep working it warns them and gives them the option of
> refreshing the session timer.

This is a very clever approach actually. The other possibility is to use the
isDirty flag in the editor. Only renew the session if isDirty is true and
once you've renewed it, set it to false again. I don't actually have a
setIsDirty JavaScript method but you can access it easily enough from
JavaScript using LiveConnect:
http://liveworks.ephox.com/hints-tips/getting-content-synchronously/

And from Dylan's suggestions:
>> 5. Implement some kind of an "autosave" every x seconds. You could use
>> javascript setTimeouts to do a periodic GetDocument and use an AJAX
>> framework to post that to a server, as a draft.

We use this in our intranet with a lot of success. The key element to it is
that it saves a draft rather than a new version. The draft is basically a
completely separate storage area specifically for autosave. So the autosaved
content doesn't get published to the site or appear in history etc. If the
user closes their browser and returns to edit the page they are asked if
they want to restore the previous draft or just start from the published
version again. For something we did because it was the easiest way to
implement it on our particular system I've been very impressed with how
effective it is. Checking isDirty would avoid the problem of users walking
away but you should make sure the system switches to a session timed out
page or users could come back and continue editing later only to find they
can't save because their session has timed out.

>> 6. Provide some kind of mechanism whereby the session can expire, but
>> the user can log back in again to recover, without losing their
>> content.

Our intranet does this as an additional line of defense. It's a lot simpler
than it sounds if you can control how authentication is done. We normally
use a HTML form to login because it's nice and user friendly, but if we
detect an unauthorized request via POST, we switch to HTTP basic
authentication (over SSL). The browser then displays it's standard
authentication dialog and resubmits the entire POST request, including data
with the authentication info. You do need to exclude the login form from
this though otherwise if the user enters invalid credentials they'll get a
HTTP auth dialog instead of a friendly incorrect password page.

Regards,

Adrian Sutton.
______________________
Adrian Sutton, CTO
UK: +44 1 753 27 2229 US: +1 (650) 292 9659 x717
Ephox <http://www.ephox.com/>
Ephox Blogs <http://planet.ephox.com/>, Personal Blog
<http://www.symphonious.net/>

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Session Problem

2008-09-02T18:14:37Z

We use option #1 in our installation, with the addition of an alert box
as part of the timeout refresh. We have the alert box, which stops JS
execution, appear about 10 minutes before the session expires. If the
user hits OK on the alert box, the AJAXy code does a roundtrip to the
server which refreshes the session timer. If they don't hit OK, the
session times out as planned. So if they walk away the session expires,
if they keep working it warns them and gives them the option of
refreshing the session timer.

- John

-----Original Message-----
From: liveworks-bounces@...
[mailto:liveworks-bounces@...] On Behalf Of Steven
Drinkwater
Sent: Tuesday, September 02, 2008 7:19 PM
To: LiveWorks Discussion
Subject: Re: [Liveworks] Session Problem

Hi Dylan,

Thanks for the very quick response :)

I was thinking of something like #1, but decided against it, because of
the drawbacks you mentioned, and could become a possible security
problem. And of course #4 was considered, but yeah, we don't want that
either ;)

#3 and #4 seem like good ideas, but I've never done Java development or
dabbled with the API in-depth, so it would take longer for me to develop
than other ideas, but might still be worth it.

#5 - Yup, I was also thinking of something along these lines, the only
problem being, is sometimes people 'play around' in the editor, and they
then might decide they don't want to keep these changes, but has been
over 'x' minutes, so we would also have to develop some kind of
roll-back-like functionality.. Again, this may actually be worth it for
us because an auto-save can't be a bad thing.

#6 - Nasteh! Good idea though, would be worth me considering.

I'll see if anyone else comes up with some ideas/suggestions and then
have a word with my client and see what he thinks, and I'll get in touch
if I need pointing in the right direction for a certain solution, if you
don't mind :)

Thanks,
Steven

On 3 Sep 2008, at 01:02, Dylan Just wrote:

> Hi,
>
> You're basically looking for a "keepalive" solution. There's a few
> options:
>
> 1. Timed AJAX keepalive. You could use something like the Prototype JS

> framework to make periodic HTTP requests to the server. As these
> requests are in the same session, your session would stay alive. I
> think Prototype has a periodic updater which could make this very
> simple.
>
> 2. You could catch editor events using Advanced APIs from Java.
> Whenever
> your raiseEvent method is called, you could call out to Javascript,
> and do an AJAX keepalive ping like above. You'd only want to do this
> on certain events, to prevent flooding the server, and locking up the
> editor. You'd need to get a reference to the "JSObject" in order to
> call out to Javascript.
>
> 3. Similar to #2, but you could make the keepalive http request from
> within Java itself. EditLive!'s internal HTTP managers keep the same
> session as the page they're within (the client cookie is passed to ELJ

> on initialization). As such, a HTTP request from within ELJ should
> keep the session alive.
>
> 4. Simply remove or increase the session timeout.
>
> 5. Implement some kind of an "autosave" every x seconds. You could use

> javascript setTimeouts to do a periodic GetDocument and use an AJAX
> framework to post that to a server, as a draft.
>
> 6. Provide some kind of mechanism whereby the session can expire, but
> the user can log back in again to recover, without losing their
> content.
>
>
> #1 is fairly straightforward, but a user can walk away and be doing
> absolutely nothing and their session would stay alive - this may not
> be desirable.
> #2 and #3 are trickier. They may need hooking into EditLive! a little
> deeper than we expose via Advanced APIs.
> #4 is the simplest, but may not meet your needs.
> #5 is fairly tricky, but gives you bonus functionality. It has the
> same "user walks away" drawback as #1.
> #6 would be tricky, but is probably the best solution in terms of
> session maintenance and user experience.
>
>
> If you have follow-up questions on the above, feel free to ask.
>
> Does anyone else on the list have any other suggestions or comments?
>
> Kind regards,
>
> Dylan Just
> Software Engineer
> Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
> www.ephox.com
>
>
>
> -----Original Message-----
> From: liveworks-bounces@...
> [mailto:liveworks-bounces@...] On Behalf Of Steven
> Drinkwater
> Sent: Wednesday, 3 September 2008 9:39 AM
> To: LiveWorks Discussion
> Subject: [Liveworks] Session Problem
>
> Hi Guys,
>
> Wondering if someone would be able to come up with a solution. We use
> a session on our site, which we time-out after 30 minutes. The session

> is checked/updated when the editor is loaded (and therefore, when
> saved). But, of course, there is a problem when they are editing for
> over 30 minutes, and haven't yet saved.
>
> Doe's anyone have a solution, to either allow me to update the session

> (I'm using PHP by the way), when an action is performed in the editor,

> or every x minutes, or something like that.
>
> Also would it be worth suggesting a save-warning timed event feature
> which could be configured in the config XML file. Which would pop-up a

> box suggesting they save or something.
>
>
> Thanks,
> Steven
> _______________________________________________
> LiveWorks@...
> List instructions at http://liveworks.ephox.com/mailing-list/
> _______________________________________________
> LiveWorks@...
> List instructions at http://liveworks.ephox.com/mailing-list/

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Session Problem

2008-09-02T17:19:12Z

Hi Dylan,

Thanks for the very quick response :)

I was thinking of something like #1, but decided against it, because
of the drawbacks you mentioned, and could become a possible security
problem. And of course #4 was considered, but yeah, we don't want
that either ;)

#3 and #4 seem like good ideas, but I've never done Java development
or dabbled with the API in-depth, so it would take longer for me to
develop than other ideas, but might still be worth it.

#5 - Yup, I was also thinking of something along these lines, the
only problem being, is sometimes people 'play around' in the editor,
and they then might decide they don't want to keep these changes, but
has been over 'x' minutes, so we would also have to develop some kind
of roll-back-like functionality.. Again, this may actually be worth
it for us because an auto-save can't be a bad thing.

#6 - Nasteh! Good idea though, would be worth me considering.

I'll see if anyone else comes up with some ideas/suggestions and then
have a word with my client and see what he thinks, and I'll get in
touch if I need pointing in the right direction for a certain
solution, if you don't mind :)

Thanks,
Steven

On 3 Sep 2008, at 01:02, Dylan Just wrote:

> Hi,
>
> You're basically looking for a "keepalive" solution. There's a few
> options:
>
> 1. Timed AJAX keepalive. You could use something like the Prototype JS
> framework to make periodic HTTP requests to the server. As these
> requests are in the same session, your session would stay alive. I
> think
> Prototype has a periodic updater which could make this very simple.
>
> 2. You could catch editor events using Advanced APIs from Java.
> Whenever
> your raiseEvent method is called, you could call out to Javascript,
> and
> do an AJAX keepalive ping like above. You'd only want to do this on
> certain events, to prevent flooding the server, and locking up the
> editor. You'd need to get a reference to the "JSObject" in order to
> call
> out to Javascript.
>
> 3. Similar to #2, but you could make the keepalive http request from
> within Java itself. EditLive!'s internal HTTP managers keep the same
> session as the page they're within (the client cookie is passed to ELJ
> on initialization). As such, a HTTP request from within ELJ should
> keep
> the session alive.
>
> 4. Simply remove or increase the session timeout.
>
> 5. Implement some kind of an "autosave" every x seconds. You could use
> javascript setTimeouts to do a periodic GetDocument and use an AJAX
> framework to post that to a server, as a draft.
>
> 6. Provide some kind of mechanism whereby the session can expire, but
> the user can log back in again to recover, without losing their
> content.
>
>
> #1 is fairly straightforward, but a user can walk away and be doing
> absolutely nothing and their session would stay alive - this may
> not be
> desirable.
> #2 and #3 are trickier. They may need hooking into EditLive! a little
> deeper than we expose via Advanced APIs.
> #4 is the simplest, but may not meet your needs.
> #5 is fairly tricky, but gives you bonus functionality. It has the
> same
> "user walks away" drawback as #1.
> #6 would be tricky, but is probably the best solution in terms of
> session maintenance and user experience.
>
>
> If you have follow-up questions on the above, feel free to ask.
>
> Does anyone else on the list have any other suggestions or comments?
>
> Kind regards,
>
> Dylan Just
> Software Engineer
> Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
> www.ephox.com
>
>
>
> -----Original Message-----
> From: liveworks-bounces@...
> [mailto:liveworks-bounces@...] On Behalf Of Steven
> Drinkwater
> Sent: Wednesday, 3 September 2008 9:39 AM
> To: LiveWorks Discussion
> Subject: [Liveworks] Session Problem
>
> Hi Guys,
>
> Wondering if someone would be able to come up with a solution. We use
> a session on our site, which we time-out after 30 minutes. The
> session is checked/updated when the editor is loaded (and therefore,
> when saved). But, of course, there is a problem when they are editing
> for over 30 minutes, and haven't yet saved.
>
> Doe's anyone have a solution, to either allow me to update the
> session (I'm using PHP by the way), when an action is performed in
> the editor, or every x minutes, or something like that.
>
> Also would it be worth suggesting a save-warning timed event feature
> which could be configured in the config XML file. Which would pop-up
> a box suggesting they save or something.
>
>
> Thanks,
> Steven
> _______________________________________________
> LiveWorks@...
> List instructions at http://liveworks.ephox.com/mailing-list/
> _______________________________________________
> LiveWorks@...
> List instructions at http://liveworks.ephox.com/mailing-list/

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Session Problem

2008-09-02T17:17:26Z

Personally I recommend #1 as it is a fairly standard solution used on
other sites with a timeout. Having said that every solution except #6
will give the user an infinite timeout while the editor is open.

On a side note:

> You'd need to get a reference to the "JSObject" in order to
> call out to Javascript.

Actually, you can do this by calling raiseEvent on the bean using action
ID TextEvent.CUSTOM_ACTION and your JavaScript function name as the
extra string :)

Andy

---
Andrew Herron, Senior Software Engineer
Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
Ephox <http://www.ephox.com> | Ephox Blogs <http://people.ephox.com>
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Session Problem

2008-09-02T17:02:23Z

Hi,

You're basically looking for a "keepalive" solution. There's a few
options:

1. Timed AJAX keepalive. You could use something like the Prototype JS
framework to make periodic HTTP requests to the server. As these
requests are in the same session, your session would stay alive. I think
Prototype has a periodic updater which could make this very simple.

2. You could catch editor events using Advanced APIs from Java. Whenever
your raiseEvent method is called, you could call out to Javascript, and
do an AJAX keepalive ping like above. You'd only want to do this on
certain events, to prevent flooding the server, and locking up the
editor. You'd need to get a reference to the "JSObject" in order to call
out to Javascript.

3. Similar to #2, but you could make the keepalive http request from
within Java itself. EditLive!'s internal HTTP managers keep the same
session as the page they're within (the client cookie is passed to ELJ
on initialization). As such, a HTTP request from within ELJ should keep
the session alive.

4. Simply remove or increase the session timeout.

5. Implement some kind of an "autosave" every x seconds. You could use
javascript setTimeouts to do a periodic GetDocument and use an AJAX
framework to post that to a server, as a draft.

6. Provide some kind of mechanism whereby the session can expire, but
the user can log back in again to recover, without losing their content.

#1 is fairly straightforward, but a user can walk away and be doing
absolutely nothing and their session would stay alive - this may not be
desirable.
#2 and #3 are trickier. They may need hooking into EditLive! a little
deeper than we expose via Advanced APIs.
#4 is the simplest, but may not meet your needs.
#5 is fairly tricky, but gives you bonus functionality. It has the same
"user walks away" drawback as #1.
#6 would be tricky, but is probably the best solution in terms of
session maintenance and user experience.

If you have follow-up questions on the above, feel free to ask.

Does anyone else on the list have any other suggestions or comments?

Kind regards,

Dylan Just
Software Engineer
Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
www.ephox.com

-----Original Message-----
From: liveworks-bounces@...
[mailto:liveworks-bounces@...] On Behalf Of Steven
Drinkwater
Sent: Wednesday, 3 September 2008 9:39 AM
To: LiveWorks Discussion
Subject: [Liveworks] Session Problem

Hi Guys,

Wondering if someone would be able to come up with a solution. We use
a session on our site, which we time-out after 30 minutes. The
session is checked/updated when the editor is loaded (and therefore,
when saved). But, of course, there is a problem when they are editing
for over 30 minutes, and haven't yet saved.

Doe's anyone have a solution, to either allow me to update the
session (I'm using PHP by the way), when an action is performed in
the editor, or every x minutes, or something like that.

Also would it be worth suggesting a save-warning timed event feature
which could be configured in the config XML file. Which would pop-up
a box suggesting they save or something.

Thanks,
Steven
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Session Problem

2008-09-02T16:38:56Z

Hi Guys,

Wondering if someone would be able to come up with a solution. We use
a session on our site, which we time-out after 30 minutes. The
session is checked/updated when the editor is loaded (and therefore,
when saved). But, of course, there is a problem when they are editing
for over 30 minutes, and haven't yet saved.

Doe's anyone have a solution, to either allow me to update the
session (I'm using PHP by the way), when an action is performed in
the editor, or every x minutes, or something like that.

Also would it be worth suggesting a save-warning timed event feature
which could be configured in the config XML file. Which would pop-up
a box suggesting they save or something.

Thanks,
Steven
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Error with Express Edit not hidding tables

2008-08-26T09:51:19Z

On 22/08/2008 17:07, "mario.blanco@..." <mario.blanco@...>
wrote:
> I am using dojo framework to set the visibility: hidden || visible instead
> of the display property to show/hide express edit. I have tried using the
> display: none || '', but his causes the applet version of Ephox to restart
> every time is shown.

Unfortunately this is a bug in IE7 and I can't really see a way for us to
add a work around. It applies to any table with a border that appears within
a section marked contenteditable="true". The only option I can see is to use
style.display = "none" instead which doesn't trigger the problem. Since that
causes applets to reload you'd have to switch which technique to use based
on whether or not express edit is in use.

The simplest way I know of to tell if express edit is in use is simply to
check if the applet is present. So if you have:
var text_value = new EditLiveJava(vapRichEditor.editLiveId,"700","400");

the check would be:

if (document.getElementById(vapRichEditor.editLiveId + "_elj")) {

It's certainly a long way from ideal so hopefully we can come up with a way
to make this easier in the future but at least this will provide a way
forward.

For the record I've logged this in our bug tracking system as EL-1035.

Regards,

Adrian Sutton.
______________________
Adrian Sutton, CTO
UK: +44 1 753 27 2229 US: +1 (650) 292 9659 x717
Ephox <http://www.ephox.com/>
Ephox Blogs <http://planet.ephox.com/>, Personal Blog
<http://www.symphonious.net/>

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Pasting from Word as clean html - remove links on headings?

2008-08-26T03:16:29Z

On 25/08/2008 12:22, "tariq.chalabi@..."
<tariq.chalabi@...> wrote:
> However when translating headings from Word documents they appear as links
> within headings - I think this is because the headings are used to build
> up the table of contents in a Word document.
> This then affects their styling.
>
> Does anyone know a way of preventing these links been carried over into
> the html?

Do you mean the HTML is something like:

<h1><a name="heading1">Heading 1</a></h1>

Short of implementing a custom paste filter there isn't a way to remove
this, however it should be fairly simple to avoid it affecting the styling.
In your stylesheet you probably have something like:

a { color: blue; text-decoration: none; }

The "a" tag serves two roles in HTML, one to be a link and one to be an
anchor or link target (which is how it's being used by the headings). If you
change your stylesheet to be:

a:link, a:visited, a:active { color: blue; text-decoration: none; }

Of course within stylesheets you can also use a:name to target just the
anchor type of links if you prefer to do it that way around.

If you want to go the custom paste filter route, take a look at
http://liveworks.ephox.com/2008/05/06/preventing-users-from-pasting-images/
and the code for the final plugin:
http://liveworks.ephox.com/plugins/filter-images/
which should give you a reasonable starting point.

Regards,

Adrian Sutton.
______________________
Adrian Sutton, CTO
UK: +44 1 753 27 2229 US: +1 (650) 292 9659 x717
Ephox <http://www.ephox.com/>
Ephox Blogs <http://planet.ephox.com/>, Personal Blog
<http://www.symphonious.net/>

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Restrict colour pallete

2008-08-26T01:43:36Z

Dylan

Thanks for letting us know. We look forward to using that feature.

Cheers

Tariq

"Dylan Just" <dylan.just@...>
Sent by: liveworks-bounces@...
25/08/2008 23:38
Please respond to
LiveWorks Discussion <liveworks@...>

To
"LiveWorks Discussion" <liveworks@...>
cc

Subject
Re: [Liveworks] Restrict colour pallete <NOT PROTECTIVELY MARKED>

Hi,

This will be a feature of the upcoming EditLive! 6.5, due for release
early September.

I'd recommend downloading our Early Access of 6.5 to test out this
feature:
http://liveworks.ephox.com/editlive-early-access/development-branch/

The config option is "colorPalette", under "wysiwygEditor". Please refer
to the documentation in that download.

Kind regards,

Dylan Just
Software Engineer
Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
www.ephox.com

-----Original Message-----
From: liveworks-bounces@...
[mailto:liveworks-bounces@...] On Behalf Of
tariq.chalabi@...
Sent: Monday, 25 August 2008 10:06 PM
To: liveworks@...
Subject: [Liveworks] Restrict colour pallete <NOT PROTECTIVELY MARKED>

hi all

Is it possible to restrict the colours available to users in the colour
palette?

There doesn't appear to be any option in the configuration file for
doing
this.

I guess the one way would be to use a stylesheet, but to my mind this
isn't as user-friendly or as flexible as the colour picker.

Kind regards

Tariq Chalabi

This communication is intended for the addressee(s) only.
Please notify the sender if received in error. Internet email
is not to be treated as a secure means of communication.
Cheshire Constabulary monitors all Internet and email activity
and requires it is used for official communications only. Thank
you for your co-operation.
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Restrict colour pallete

2008-08-25T15:38:11Z

Hi,

This will be a feature of the upcoming EditLive! 6.5, due for release
early September.

I'd recommend downloading our Early Access of 6.5 to test out this
feature:
http://liveworks.ephox.com/editlive-early-access/development-branch/

The config option is "colorPalette", under "wysiwygEditor". Please refer
to the documentation in that download.

Kind regards,

Dylan Just
Software Engineer
Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
www.ephox.com

-----Original Message-----
From: liveworks-bounces@...
[mailto:liveworks-bounces@...] On Behalf Of
tariq.chalabi@...
Sent: Monday, 25 August 2008 10:06 PM
To: liveworks@...
Subject: [Liveworks] Restrict colour pallete <NOT PROTECTIVELY MARKED>

hi all

Is it possible to restrict the colours available to users in the colour
palette?

There doesn't appear to be any option in the configuration file for
doing
this.

I guess the one way would be to use a stylesheet, but to my mind this
isn't as user-friendly or as flexible as the colour picker.

Kind regards

Tariq Chalabi

This communication is intended for the addressee(s) only.
Please notify the sender if received in error. Internet email
is not to be treated as a secure means of communication.
Cheshire Constabulary monitors all Internet and email activity
and requires it is used for official communications only. Thank
you for your co-operation.
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Restrict colour pallete

2008-08-25T05:05:49Z

hi all

Is it possible to restrict the colours available to users in the colour
palette?

There doesn't appear to be any option in the configuration file for doing
this.

I guess the one way would be to use a stylesheet, but to my mind this
isn't as user-friendly or as flexible as the colour picker.

Kind regards

Tariq Chalabi

This communication is intended for the addressee(s) only.
Please notify the sender if received in error. Internet email
is not to be treated as a secure means of communication.
Cheshire Constabulary monitors all Internet and email activity
and requires it is used for official communications only. Thank
you for your co-operation.
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Pasting from Word as clean html - remove links on headings?

2008-08-25T04:22:14Z

Hi all

Just started using new Ephox editor in IBM's Websphere Portal and so far
we're pleased with the results - a big improvement on the IBM offering.
We do have a couple of configuration issues though..

We are using the "paste as clean HTML" option for word imports. I must
say it does a good job of translating the Word formatting into html.

However when translating headings from Word documents they appear as links
within headings - I think this is because the headings are used to build
up the table of contents in a Word document.
This then affects their styling.

Does anyone know a way of preventing these links been carried over into
the html?

Regards

Tariq Chalabi

This communication is intended for the addressee(s) only.
Please notify the sender if received in error. Internet email
is not to be treated as a secure means of communication.
Cheshire Constabulary monitors all Internet and email activity
and requires it is used for official communications only. Thank
you for your co-operation.
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: FIXED. percent and plus sign causes ExpressEdit not to work

2008-08-24T16:09:19Z

Hi,

The error indicates that you are not URL-encoding the content when
passing it to setBody(). When content is URL-encoded, the % and + signs
are used as 'escape' characters, to encode certain characters, e.g.
"%20" for a space.

Your content has a % in it, but the characters following it do not code
for an actual character - as such, the error message is complaining
about an "invalid escape sequence".

We recommend that URL-encoding be done server-side, however, encoding
with Javascript's encodeURIComponent() function also works.

Kind regards,

Dylan Just
Software Engineer
Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
www.ephox.com

-----Original Message-----
From: liveworks-bounces@...
[mailto:liveworks-bounces@...] On Behalf Of
mario.blanco@...
Sent: Saturday, 23 August 2008 5:14 AM
To: liveworks@...
Subject: Re: [Liveworks] FIXED. percent and plus sign causes ExpressEdit
not to work

mario.blanco@... wrote:
>
> http://www.nabble.com/file/p19113673/setBodyErrorIE.png
> http://www.nabble.com/file/p19113673/setBodyErrorFF.png
>
> When using the setBody() method and passing any string that constains
a

> percent sign % or plus sign +, Express Edits generates an error (see
> attached screenshots).
>
> Is there a method I need to parse the string before passing it to
> setBody()?
>
> EditLive version: 6.3.7.118
> IE: 7.0
> FF: 2.0
>

Needed on encode the string by using encodeURIComponent()
(http://developer.mozilla.org/En/Core_JavaScript_1.5_Reference:Global_Fu
nctions:encodeURIComponent)
--
View this message in context:
http://www.nabble.com/percent-and-plus-sign-causes-ExpressEdit-not-to-wo
rk-tp19113673p19113852.html
Sent from the LiveWorks! mailing list archive at Nabble.com.

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: FIXED. percent and plus sign causes ExpressEdit not to work

2008-08-22T12:14:21Z

mario.blanco@vignette.com wrote:

When using the setBody() method and passing any string that constains a percent sign % or plus sign +, Express Edits generates an error (see attached screenshots).

Is there a method I need to parse the string before passing it to setBody()?

EditLive version: 6.3.7.118
IE: 7.0
FF: 2.0

Needed on encode the string by using encodeURIComponent()
(http://developer.mozilla.org/En/Core_JavaScript_1.5_Reference:Global_Functions:encodeURIComponent)

percent and plus sign causes ExpressEdit not to work

2008-08-22T12:02:31Z

When using the setBody() method and passing any string that constains a percent sign % or plus sign +, Express Edits generates an error (see attached screenshots).

Is there a method I need to parse the string before passing it to setBody()?

EditLive version: 6.3.7.118
IE: 7.0
FF: 2.0

Re: Error with Express Edit not hidding tables

2008-08-22T09:07:31Z

ephoxExpressEditError.txt

Adrian,

Thanks for your quick reply. I have attached pieces of Javascript and HTML code that I am using to show/hide and work with ExpressEdit.

I am using dojo framework to set the visibility: hidden || visible instead of the display property to show/hide express edit. I have tried using the display: none || '', but his causes the applet version of Ephox to restart every time is shown.

Thanks for taking a look and let me know if you need anything else from me.

Thanks,

Mario

Adrian Sutton wrote:

On 21/08/2008 21:57, "mario.blanco@vignette.com" <mario.blanco@vignette.com>
wrote:
> mario.blanco@vignette.com wrote:
>>
>> http://www.nabble.com/file/p19096700/errorHideExpressEdit.png
>>
>> The attached screen shot shows that when hidding expressEdit the <table>
>> inside expressEdit don't hide.
>>
>> What is causing this issue?

Hi Mario,
That's certainly an interesting case. Does it only happen in IE7? It looks
a lot like the table isn't inheriting the display: none that I assume you're
using to hide express edit. Could you send through the HTML you're editing?
It's probably also worth checking you don't have a stylesheet applied that
sets table's to display: table or display: block or something which would
cause them to reappear.

Regards,

Adrian Sutton.
______________________
Adrian Sutton, CTO
UK: +44 1 753 27 2229 US: +1 (650) 292 9659 x717
Ephox <http://www.ephox.com/>
Ephox Blogs <http://planet.ephox.com/>, Personal Blog
<http://www.symphonious.net/>

_______________________________________________
LiveWorks@liveworks.ephox.com
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Error with Express Edit not hidding tables

2008-08-22T07:11:30Z

On 21/08/2008 21:57, "mario.blanco@..." <mario.blanco@...>
wrote:
> mario.blanco@... wrote:
>>
>> http://www.nabble.com/file/p19096700/errorHideExpressEdit.png
>>
>> The attached screen shot shows that when hidding expressEdit the <table>
>> inside expressEdit don't hide.
>>
>> What is causing this issue?

Hi Mario,
That's certainly an interesting case. Does it only happen in IE7? It looks
a lot like the table isn't inheriting the display: none that I assume you're
using to hide express edit. Could you send through the HTML you're editing?
It's probably also worth checking you don't have a stylesheet applied that
sets table's to display: table or display: block or something which would
cause them to reappear.

Regards,

Adrian Sutton.
______________________
Adrian Sutton, CTO
UK: +44 1 753 27 2229 US: +1 (650) 292 9659 x717
Ephox <http://www.ephox.com/>
Ephox Blogs <http://planet.ephox.com/>, Personal Blog
<http://www.symphonious.net/>

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

Re: Error with Express Edit not hidding tables

2008-08-21T13:57:44Z

mario.blanco@vignette.com wrote:

The attached screen shot shows that when hidding expressEdit the <table> inside expressEdit don't hide.

What is causing this issue?

I forgot to include:
Browser used: IE 7
EditLive/ExpressEdit version: Version: 6.3.7.118

Error with Express Edit not hidding tables

2008-08-21T13:54:04Z

The attached screen shot shows that when hidding expressEdit the <table> inside expressEdit don't hide.

What is causing this issue?

Re: check if license has expired

2008-08-20T14:59:47Z

Hi,

Sorry, this is not possible.

Kind regards,

Dylan Just
Software Engineer
Global: +1 (650) 292 9659 x705 Australia: +61 (7) 3858 0100
www.ephox.com

-----Original Message-----
From: liveworks-bounces@...
[mailto:liveworks-bounces@...] On Behalf Of
mario.blanco@...
Sent: Wednesday, 20 August 2008 5:13 AM
To: liveworks@...
Subject: [Liveworks] check if license has expired

How can I check if the EditLive license has expired with JavaScript?
--
View this message in context:
http://www.nabble.com/check-if-license-has-expired-tp19056749p19056749.h
tml
Sent from the LiveWorks! mailing list archive at Nabble.com.

_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/
_______________________________________________
LiveWorks@...
List instructions at http://liveworks.ephox.com/mailing-list/

check if license has expired

2008-08-19T12:13:24Z

How can I check if the EditLive license has expired with JavaScript?