Bugs and Problems in Oscailt Code

place any bugs here.

• I posted on it today 2005/10/22 and noticed some strange date indications at the preview level of the posting process (date 1970!)

-- ChekovFeeney - 25 Aug 2005

• During installation, give the user a chance to set their location of 'curl' - oscailt install defaults to /usr/local/bin/curl, and that isn't always the location of curl (for my setup for example it is located in /usr/bin/curl). as it is, a person has to go in and manually edit the config (specifically, objects/magpie/snoopy.inc)to get curl to work.

-- JenkA - 29 Nov 2006

• Default database setup results in this mysql error: PRIMARY and INDEX keys should not both be set for column `story_id`. Trying to change it results in Oscailt error. (Mysql -v: mysql Ver 14.12 Distrib 5.0.22)

-- JenkA - 29 Nov 2006

• Using the 'basic indymedia' install, the gallery module fails with this error: database error : 1054 - Unknown column 's.story_id' in 'on clause'. Looking at the mysql query, it seems that 's.story_id' is being called before 's' is defined. Here is the query I'm talking about (for gallery display):

SELECT a.attachment_id, a.story_id, a.comment_id, UNIX_TIMESTAMP( a.time_posted ) , a.attachment_file, a.description, a.image, a.video, a.audio, a.hidden, a.featurized FROM imemc_attachments AS a '>>this line is the error >>> LEFT JOIN imemc_comments AS c ON s.story_id = c.story_id
LEFT JOIN imemc_stories AS s ON s.story_id = a.story_id WHERE ..... etc.

-- JenkA - 03 Dec 2006

• When updating data objects in Administration -> Site Section Administration, after successfully updating the object there are several options. * Oscailt Administration * Finish Editing Object and return to the page that you started at. * Edit Again * View the object on its main page: View updated object on test site. | View current object on live site. * Browse Live site. * Browse Test site.

But the "Finish Editing Object and return to the page that you started at" link doesn't return the user back to the listing page for the modules they have just updated. Instead it links to 'Create a new module' for whatever type has just been edited.

-- JenkA - 03 Dec 2006

• Here is a strange bug: I have added several types of editors in the 'roles' section. But if the 'role' includes permission to 'edit stories', that editor cannot publish. Instead, when the editor goes to publish a new story, the preview appears, but when it is submitted to actually publish, there is a MySQL error: 'INSERT INTO' is replaced with 'UPDATE' query, which is wrong, and prevents the publishing of a new story by that editor.