Persistent error when trying to change album cover after photo upload and submission. "Photo too small" This happens for any size photo.
Persistent error when trying to change album cover after photo upload and submission. "Photo too small" This happens for any size photo.
Edit Photo Album coveri get the same
Persistent error when trying to change album cover after photo upload and submission. "Photo too small" This happens for any size photo.
For the past year ALL of my posts have outlined legitimate bugs in the software, or outlined real concerns that applied not only to myself but to to other users. You can verify this by searching the forums. If you do not have the time or are too busy to provide constructive answers to these, or confirm the bugs, then please direct them to someone who has the time. I posted supplementary information and did the tests you asked and provided feedback. Please do not insult me by referring me to forum rules especially after I am testing for the benefit of all users and even defended the team against detractors.
The problem is a database problem related to the user field. E.g. if we import data into user field on new installation it gives the error. It also gives the error after you have upgraded your platform from say 1.53 to 1.7. In a brand new install it gives no problem. (empty database) Maybe cache needs to be cleared in database? or import additional tables related to photo plugin?
@Omari
We recently upgraded from 1.6 to 1.7 and the ability to edit the album images are fully functional, so I hope this helps with you diagnosis of your issue.
--Robert--
-----------------
define('OW_USE_AMAZON_S3_CLOUDFILES', true); // whether or not to use AMAZON S3define('OW_AMAZON_S3_ACCESS_KEY', '{your_access_key}'); // access keydefine('OW_AMAZON_S3_SECRET_KEY', '{your_secret_key}'); // secret keydefine('OW_AMAZON_S3_BUCKET_NAME', '{bucket_name}'); // the name of the bucket for recording datadefine('OW_AMAZON_S3_BUCKET_URL', '{bucket_url}'); // url of the bucket for recording data (for example, http://test.s3.amazonaws.com/)
-----------------
the result is this error message
When I turn off clouds the error doesn't occur