Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

DataObjectManager Module /

Discuss the DataObjectManager module, and the related ImageGallery module.

Moderators: martimiz, UncleCheese, Sean, Ed, biapar, Willr, Ingo, swaiba

Uploadify Frontend Error

Go to End

5 Posts   3170 Views


Community Member, 6 Posts

14 October 2010 at 3:07am

Edited: 14/10/2010 3:07am


I am getting weird errors on my Uploadify-Fields when using in frontend.
On one page i can create a post (mydomain/myadmin/add-post) evertyhing works fine.
On the edit page (mydomain/myadmin/edit/3) the attached files are show correctly, but when i try to delete an attachement i am getting the javascript error:

 Failed to load resource: the server responded with a status of 500 (Warning: "popCurrent called on ModelAsController controller, but it wasn't at the top of the stack" at line 454 of ABSPATH_TO_SILVERSTRIPE_PROJECT/sapphire/core/control/Controller.php

Another failure appears when I try to add a new attachment
Any ideas or solutions?

Thanks in advance.


Community Member, 6 Posts

14 October 2010 at 10:45am

It definitively has something to do with the URL.
I wrote a new Class and created a page with this class at the sitetree's root level.
At least the upload and delete functions are working. Unfortunatly the has_many-relations don't, but this could be caused by my faulty test-script.


Community Member, 6 Posts

16 October 2010 at 10:53am

I found the solution:

I had to use Director::addRules($prio,$rule).


Community Member, 24 Posts

26 January 2011 at 2:17pm

What rule did you add to Director::addRules?


Community Member, 41 Posts

14 June 2011 at 5:16am

techguyver or DNA, did you figure this out? I'm getting the same thing, but I can't seem to figure out why . . .