hiphopsmurf

The size limit is based on the amount of available memory for your environment and the settings within your php.ini file. All files uploaded via this plugin get loaded into memory before being sent to Dropbox (out of my control).

This is caused by another plugin on your site that is using dropbox.

That is always an option :O)

@alin Marcu They have known about this issue since June and have still not updated it.

The size limit only depends on the amount of memory available to your site and is usually controlled via the php.ini file. The default limit in the php.ini file is 2 megabytes and can often be overridden depending on your host.

The issue your probably having is related to the permissions set on your uploads folder, Usually located at (in your case):

/web/htdocs/www.knockcubed.com/home/wp-content/uploads/

That folder should should have the permissions set to: 0755

In the plugin, the Upload directory should be set to:

/web/htdocs/www.knockcubed.com/home/wp-content/uploads/SOME-FOLDER-NAME

where “SOME-FOLDER-NAME” is whatever you would like.

You should be able to use something like this:

<?php echo do_shortcode('[simple-wp-dropbox]'); ?>

The problem you are seeing is that someone forgot an equal sign in file plugins/wysija-newsletters/helpers/front.php on line 241

strpos($content, '[wysija_page]') == false
Should be
strpos($content, '[wysija_page]') === false

This is due to a conflict with another plugin. Likely Backup to Dropbox.

Sorry but I will not be restoring the code. If someone is an advanced user and wants that information, they will know where to find it. Considering your a plugin developer and have plugins published here on wordpress you should know how to use Trac.

You are welcome to keep this issue open as long as you would like. This is not a support issue and has been marked as such. If you feel that strongly about this issue, please direct further communication to support[at]wordpress[dot]org

Thanks!

Removing the files from the repository prevents someone from attempting to use a version that would open their server up to having a malicious script uploaded. Anyone doing “Research” could clearly find what the exploit was without the files on the repo and also confirm that the files were removed completely.

Sorry that I don’t feel compelled to rehash an issue that has already been resolved, but if you feel like you hit a dead end in your research and need pointed in the direction of where to look, feel free to email me directly and I will be happy to help.

Thanks!

Hi Dan,

I can assure you that though I did not catch the bug before it was publicly posted, I was quick to remove the multiple upload functionality along with the effected files and if you would’ve checked the developers page you would’ve seen that I also removed all previous versions including ones that did not contain the security whole. Please do the proper research before spouting off. Thanks!

I will look into it.

It will be with any luck fixed this weekend.

It is a conflict with Backup to Dropbox.