Constant prompts for FTP credentials after 2.0.6 upgrade

Ai1ec requires write privileges as the webserver user to the directory …../wp-content/plugins/all-in-one-event-calendar/cache/

If WP can’t write to a particular directory, it will prompt you for FTP access so it can try and use that to access the files. Unfortunately Ai1ec writes a lot of files in that directory, so you will get asked a lot of times, and even then it might not work as expected.

I would check the permissions of this directory if at all possible.

Note: If you go to Dashboard -> Events -> Settings then go to the Advnaced tab and then select “Cache Report” from the pulldown, it should tell you if it thinks the directory is writable by the webserver user.

Thanks for that. For good measure I gave full public (and group) write permissions to that directory and it didn’t help. I checked the cache report and it confirms the directory is writable. Unfortunately I’m still getting prompted for FTP credentials every time any admin page is accessed.

Do you have any other suggestions?

Not attempting to hijack here; just hoping to add related details. I’m in a really similar boat. Cache report indicates the directory is writable yet get prompts for FTP credentials intermittently. (running WP 3.9 and hadn’t installed Ai1ec plugin until yesterday – fresh 2.0.6)

Same here also. Even I made all files and folders in all in one calendar plugin writable and no change, wants ftp credentials. But I have also another problem, all links in admin menu are missing.

same also here, 2.0.6. works not good, on backend and frontend asks everwhere for FTP login data. Terrible.

Someone from Time.ly posted a “quick work-around” here (see post #12):

https://community.time.ly/forum/troubleshooting/general_aa/14645-upgrade-breaks-admin

That workaround works for me. But clearly the workaround just prevents the execution of code that is presumably required so hopefully a proper fix will be provided soon.

Definitely, but as mentioned by Lukasp, it’s a quick work-around, not an end-to-end fix.

I’m assuming the fix will be in the next update, but that depends just how complex the underlying issue is.