Hi,

I have installed all related modules according to the instructions however when I click on create a new image gallery page it doesn't appear in the cms like all the other pages do. After a refresh it does appear however for me to use it I have to save it which when I click on says there's been an error while saving.

Could someone please confirm if the image gallery module does or doesn't work with silverstripe 2.3.4? If it does, what additional steps need to be taken to get it to work?

Thanks.

The bug he's reporting sounds different, though. In any case, the latest rev of DOM has added 2.3.4 compliance.

SStripeS, I'm having the exact same problem. Did you get it working? If so, what versions of image-gallery, DOM etc did you use?

I'm having this exact same problem, except with SS 2.4.2.

create new imagegallery page, nothing appears in the site tree menu until I refresh the page but I get firebug reporting this error message when I create the page:

POST http://kenpo-karate-co-nz.mccoy.techservers.net/admin/AddPageOptionsForm
   
500 There has been an error
      808ms   
base.j...6444156 (line 61)
ParamsHeadersPostPutResponseCacheHTML

There has been an error

When I try to save/save and publish the imagegallery page it says 'error saving content' and firebug reports this error:

POST http://kenpo-karate-co-nz.mccoy.techservers.net/admin/EditForm
   
500 There has been an error
      1.39s   
base.j...6444156 (line 61)
500//There has been an error
errorMessage(msg="Error saving content", fullMessage="500//There has been an error")leftan...6444159 (line 367)
msg = "Error saving content"
fullMessage = "500//There has been an error"
onFailure(response=XMLHttpRequest { onreadystatechange=[xpconnect wrapped nsIDOMEventListener], readyState=4, more...})leftan...6444159 (line 448)
response = XMLHttpRequest { onreadystatechange=[xpconnect wrapped nsIDOMEventListener], readyState=4, more...}
header()base.j...6444156 (line 67)
processOnDemandHeaders(xml=XMLHttpRequest { onreadystatechange=[xpconnect wrapped nsIDOMEventListener], readyState=4, more...}, status=500, _ondemandComplete=function())base.j...6444156 (line 746)
xml = XMLHttpRequest { onreadystatechange=[xpconnect wrapped nsIDOMEventListener], readyState=4, more...}
status = 500
_ondemandComplete = function()
prototypeOnDemandHandler(xml=XMLHttpRequest { onreadystatechange=[xpconnect wrapped nsIDOMEventListener], readyState=4, more...}, status=500, callback=function())base.j...6444156 (line 749)
xml = XMLHttpRequest { onreadystatechange=[xpconnect wrapped nsIDOMEventListener], readyState=4, more...}
status = 500
callback = function()
header(readyState=4)base.j...6444156 (line 70)
readyState = 4
onStateChange()base.j...6444156 (line 66)
bind()base.j...6444156 (line 29)
[Break On This Error] console.error(fullMessage);}
leftan...6444159 (line 367)

Exact same thing happens if I create a new page (standard page type) and try to change the page type to imagegallery page under the behaviour tab.

I've tried removing and reinstalling the imagegallery, DOM and uploadify modules, installing different versions of them including the most recent versions and still get the same problem.

Also, at one stage I managed to get the imagegallery page to save after being created, uploaded a couple of images to the default album and THEN got the 'error saving content' message, deleted that page and tried to delete the image gallery folders from the 'files and images' tab but got another error when i clicked on the folder, and again when I tried to delete it.

Have tried reading through the errors in depth but I'm not great at debugging javascript and I'm just not seeing where the cause of the errors are.

Oddly enough, I have 2 other websites on the same server as the one experiencing this issue, both running SS2.4.2 with image gallery, DOM and uploadify and didn't have any problems at all with them, and another website on that same server running SS 2.3.4 with imagegallery, DOM and SWFupload and that HAD the same problem when I first built it, but it came right and fixed itself after reinstaling the modules.

I'm completely lost on how to fix this one .. help please