[
https://issues.apache.org/jira/browse/ROL-2007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14032523#comment-14032523
]
Greg Huber commented on ROL-2007:
---------------------------------
It seems to happen when you do a search and then try and edit/save the file.
There is a tiles result .MediaFileEditSuccess which calls
parent.onEditSuccess();
where it used to call (caused a firefox issue and now a post warning message):
window.location.reload(true); // Endless refresh loops in FF
and was replaced with:
window.parent.location = window.parent.location.href;
but this did not pass the weblog parameter neded, hence the error message.
Fix use :
window.parent.location = window.parent.location.href + "?weblog="+<s:property
value="%{actionWeblog.handle}" />;
or
$("#mediaFileSearchForm").submit();
the latter, and preferred as it matches more closely what
window.location.reload(true); used to do.
Committed revision 1602889.
> Changing values in Media File Editor frequently results in permissions error.
> -----------------------------------------------------------------------------
>
> Key: ROL-2007
> URL: https://issues.apache.org/jira/browse/ROL-2007
> Project: Apache Roller
> Issue Type: Bug
> Components: Media files / uploads
> Affects Versions: 5.1
> Reporter: Glen Mazza
> Assignee: Greg Huber
>
> The Media File Editor (the popup that appears when you click on any of the
> media files on the Media Files page) frequently returns the below error when
> changing and trying to save new values on that page:
> Permission Denied
> Possible causes:
> You requested a weblog entry that you do not have permission to edit
> (perhaps one you''ve already submitted for review?).
> You tried to save an object from "stale" web page, left by an earlier
> login under a different user account.
> You logged in using incorrect capitalization of your username. To resolve
> this problem, logout and login again with your correct username.
> Your blog server''s database connection is misconfigured. To resolve this
> problem, see your system administrator.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
