Inserting an image "You cannot perform this action..."

[pedromiel]

I see from earlier posts that users are struggling to add links and are seeing
the error "You cannot perform this action in this area of the page". I am
getting the same error when trying to insert an image. No reason why I should
start to get this error. I've inserted images on this page before. But then
Contribute does seem to start doing (or not doing) things of it's own accord.
I have tried using the <p></p> fix that other users say work fo rlinks but it
doesn't work for images. Frustrated.

[jigatron]

I'm having the same issue. I am using Contribute 4, the website in question was
built with DIV positioning, but the editable regions are nested in a table. I
can edit the text perfectly, but when I try to insert an image Contribute pops
up an error saying "you cannot do perform this action in this region of the
page".

Any suggestions?

[Rosemary Neave]

I have a similar issue. I am not using templates at all. I can add text, but
not links or images, and I can not delete the row involved. It feels like a bug

One minute I am editing OK, next there is this "you can not perform this
action" notice. It is as if I have inadvertantly changed something that can
now not be unchanged. I am not a techo, just simply editing a basic site in
contribute.

look forward to solutions. I am using Contribute 3, but it seems the same
issue is in contribute 4

[jigatron]

Ok... I figured out the issue that we were having. It was definitely our error
and not a bug.

It's complicated and I'm not sure if anyone else would have the same issue -
but I'll explain it anyway.

We actually had 2 templates in the one file which was confusing Contribute. We
had our main page template, then we had a small news template that was loaded
in as an ASP include. The problem arose because I was editing within the
editable region of the main template, but the included template was telling
Contribute that we couldn't edit anywhere outside it.

Like I said, complicated - but it might help others with the same issue.

[allsoft]

I've encountered the same issue now. Site was created with divs and no tables.
For me it comes up when trying to add an image. Links seems to work fine.
There are no embedded templates so jigatron's solution won't work for me.

Did anybody else have luck with this issue?

[Rosemary Neave]

One error of my own making I found was a wrongly designated anchor - I had
#anchor#anchor - ie i had accidently put the anchor in twice. I could not
edit the anchor so my admin person had to, once this was fixed access seemed OK.

[allsoft]

I had a double check of the links in my webpages.
Unfortunately none of them were as you had described.
So looks like I'm still baffled on what's causing this one.
I've run my pages through the w3 validator and it only has issue with missing
alt tags.

[Strontium_99]

I might be able to shed a little light on one possible reason for this and I
believe it to be a bug in Contribute.

This only seems to happen on .asp pages where you have Flash that you are
feeding URL variables into it.

If you edit any editable region on the page for some reason Contribute wants
to bung:
<MM:BeginLock unremovable type="MM_EDITTEXTONLY" orig="%3C%25=vname%25%3E">
Into my Flash code, thus corrupting the whole page code and totally confusing
Contribute. And this happens even if you are editing a region totally unrelated
to the Flash code?!?!?!?!??!?!?!?!

I tried to take this up some time ago with Adobe support who were so unhelpful
I gave up and rewrote the pages as standard .html and used template variables
instead.

[allsoft]

@Strontium_99: while it might happen with flash & asp as well but my website
was static html pages (no dynamic content server-side or client-side).
additionally my website had no flash elements.

however in the end i did end up resolving the issue after around 4 hours of
stripping down the dwt.
broken section of markup looked like:

<div>
<p>Some Text In Here</p>&nbsp;
</div>

fixed section of markup looked like:

<div>
<p>Some Text In Here</p>
</div>

might not be the issue everyone is encountering, but this resolved the
problems i was having