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're retiring the forums!

The SilverStripe forums have passed their heyday. They'll stick around, but will be read only. We'd encourage you to get involved in the community via the following channels instead:

General Questions /

General questions about getting started with SilverStripe that don't fit in any of the categories above.

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

Media (Image) Upload Problem

Go to End

11 Posts   2278 Views


Community Member, 23 Posts

16 October 2012 at 4:35am

Using a standard install of v3.0.2, when I upload an image into an RTE through the "media" icon it then proceeds to list EVERY image that I've uploaded since the last flush.

Clicking Insert proceeds to insert all the images, which is obviously not what I want, so I have to remove all items other than the one I uploaded.

Also, the alignment options are only available for the first image listed, which is never the most recently uploaded file as they display in chronological order. Which means after removing all of the unwanted images and inserting the correct one, I have to adjust the alignment by revisiting the media tab.

This happens even if I'm uploading the images to a different page.

Bug or feature? Any word on a planned fix / tidy?


Forum Moderator, 1391 Posts

16 October 2012 at 5:53am

Hi feejin,

I ran into that same problem, and was wondering if this is by design for some reason , a bug or some caching issue? At least it doesn't try to upload those files again :-)

Did you spot an existing ticket for this behaviour?


Community Member, 69 Posts

16 October 2012 at 7:50am

I ran into the same problem to. Mostly its not a problem, but sometimes annoying.


Community Member, 23 Posts

16 October 2012 at 9:16pm

Edited: 16/10/2012 9:18pm

One of the SilverStripe devs replied to me on Twitter, it's a known bug with an open ticket:

It's been on critical priority since RC1 so hopefully will be done for 3.0.3.

For me, it's annoying. But not sure how I'm going to explain it to clients who maintain their own pages.


Administrator, 690 Posts

17 October 2012 at 9:10am

Yeah - we're going to push to get this one resolved in 3.0.3.


Administrator, 25 Posts

17 October 2012 at 9:15am

G'day Team,

Thanks for raising these issues. Sometimes it's not easy to tell what people are most interested in seeing fixed and we appreciate that you've all been open about it.

NOW...although the date has not yet been set for the 3.0.3 milestone, after talking to Sam, it's been moved into the milestone and will hopefully be assigned soon.

So. Anyone feel like having a crack at it? ;)


Community Member, 23 Posts

18 October 2012 at 4:55am

Good news, thanks chaps! We tend to hand sites over to clients to maintain so bugs they're going to notice are the ones I like to see fixed :)


Community Member, 97 Posts

24 January 2013 at 10:41pm

it looks like we still have this problem in 3.0.3. has it been fixed?

Go to Top