A very small bug has snuck into the dataobject_manager.css file on line 154. The background url declaration looks like this url(../images/closebox.png') which nerfs the background image. Just adding the first ' in the parenthesis should fix it.
297 Posts 52893 Views
Thanks. Fixed that.
When running the latest revision of DataObjectManager against trunk (89463), I get the following error when attempting to access a page that uses DAO:
"Trying to get property of non-object" at line 681 of C:\xampp\htdocs\members\dataobject_manager\code\FileDataObjectManager.php
return isset($img) ? $img->CroppedImage(50,50)->URL : $file->Icon();
Check on the integrity of that file. It exists in the database, but CroppedImage() is returning false, so it either doesn't exist on the server or it's not readable.
Thanks, UncleCheese. You were correct--the file didn't exist.
I have a screen shot but don't see a way of attaching it to this forum post.
Hit another issue:
When using DAO to upload an image, "SecurityID doesn't match, possible CRSF attack." is displayed after uploading the image then clicking "finish" on the extra data page. This appears to be caused by the fact that the extra data page's SecurityID field has a blank value:
<input type="hidden" id="FileDataObjectManager_Popup_EditUploadedForm_SecurityID" name="SecurityID" value="" />
If I check the value of Session::get('SecurityID') (used by Form.php on line 434 to populate SecurityID's value), it is set correctly.
In general, the SecurityID field seems to be populated correctly. The initial DAO popup window has a SecurityID field with a value (as it should):
<input type="hidden" id="FileDataObjectManager_Popup_UploadForm_SecurityID" name="SecurityID" value="15856" />
Hi again Uncle,
I'm still having the problem where if I upload an image in 'Files & Images' to a subfolder, the files go straight into the root of the assets folder and not into the folder I want them to.
I'm not getting any errors. Where do you think is the best place to put some debug statements so I can see what's going on?
(I'm also using subsites & cmsworkflow modules although don't know if that would affect uploads or not.)
Any help much appreciated!
i also stumbled over this odd behaviour, which is well known in SS bug tracker:
seems to be fixed in trunk but it unfortunately didn't get it into the 2.3 branch