Support Forum

This just gets stranger.

So it looks like the original problem may be that folders can not be automatically created. Then when you activate the uploader plugin it fails to create the folders so also then stops the install and does not create the new db table either. At least that is my best guess.

So as well as creating the new folders you need the real issue then is working out why they can not be created and that will most often come down to permissions on the server. Can you check them? They should be the same as those set up for the wp-content folder of which they are a grand-children.

But you will also need to check the UID/GUID values on those folders to ensure they have the correct ownership. If you do not know how to check this then to be honest the best and easiest way is to ask your hosting support to check them all to ensure that new folders can be both created and written to by the php software.

Someone will be here...

Well that is, of course, good news - but doesn't explain why the install failed to create the folders you needed. The only other thing that comes to mind would be something like an .htaccess rule that prevents it.

It probably means that you will need to create these manually. By default they are named (under the sp-resources folder):

forum-image-uploads
forum-media-uploads
forum-file-uploads

If we still need to create the missing table manually will you be able to do that with a sql script that you can run form phpmyadmin?

Weirder and weirder then!

This is the SQL to create the table.

CREATE TABLE `XXX_sfpostattachments` (
 `attachment_id` bigint(20) NOT NULL AUTO_INCREMENT,
 `post_id` bigint(20) NOT NULL,
 `topic_id` bigint(20) NOT NULL,
 `type` varchar(10) NOT NULL,
 `path` varchar(250) NOT NULL,
 `filename` varchar(100) NOT NULL,
 `size` int(11) NOT NULL,
 PRIMARY KEY (`attachment_id`),
 KEY `post_id_idx` (`post_id`),
 KEY `topic_id_idx` (`topic_id`)
);

Of course you do need to change the 'XXX' for your own table prefix (default of course of 'wp_).