Support has been upgraded!
The Support Forum is closed. Not to worry! Providing the top quality support you expect and we're known for will continue! We're not ending support, just changing where you submit requests. This will provide you with the best experience possible.
Premium Support
Have you purchased an addon for Connections such as one of our premium templates or extensions with a valid license and you need help?
Please open a Support Ticket in your user account.
Free Support
Are you using the free Connections plugin? Don't worry, you are still very important to us! We are still providing you with the same high quality support that we're known for.
Please open a new support topic in the WordPress support forums for Connections.
Tagged: 8.28.2
- This topic has 16 replies, 4 voices, and was last updated 4 years, 11 months ago by
Michael Chuchro.
-
AuthorPosts
-
10/08/2018 at 4:25 pm #474363
Michael Chuchro
ParticipantI get the same error with the email log plugin.
ok, so it appears that any new plugin i install and then try to activate throws the error message. However any plugin that I had previously installed can be activated and deactivated without any problems. I have a few plugins installed but do not keep them activated. I am able to activate them without any issues.
10/08/2018 at 5:10 pm #474368Steven Zahm
Keymaster@ Michael
It is not so much as new vs existing…
It is not uncommon for plugins to need the file in question to ensure the tables that it requires are up to date. This is what Connections is doing. It is checking that the tables are current so it know of it needs to runs any db upgrades or not.
It could be that the other existing plugins do not have any database tables. So there would be no need for them to load that file and would not generate a error.
Since you’ve updated Connections in the past without issue, I suspect that GoDaddy may have changed something on their servers which is causing this issue for you. I would suggest contacting GoDaddy support to let them know of this issue. Perhaps this is something the can quickly correct.
Also, if you send me an FTP login, I can take a look at the permissions of the files and tweak them so the files can be loaded by WP.
I’ll also need a temp WP admin. You can use this plugin to create it:
https://wordpress.org/plugins/temporary-login-without-password/
I do not think it requires any database tables so it should install and work without any issues.
Reply back, as a private reply, with the login details for FTP and the temp WP admin login link.
10/09/2018 at 3:14 pm #474476Steven Zahm
Keymaster@ Michael
Checking to see if there was any progress. If you can send me the accesses I asked for, I can take a look.
10/09/2018 at 3:31 pm #474477Jayson Gurney
ParticipantThis reply has been marked as private.10/09/2018 at 4:07 pm #474480Michael Chuchro
ParticipantThis reply has been marked as private.10/10/2018 at 1:03 pm #474601Steven Zahm
Keymaster@ Michael
Ok, that
install.php
file was placed on the server 8/3/2018. So, either GoDaddy put it there or it was added by a plugin. My vote is on GoDaddy based on that support thread I found and shared with you.This file is not part of the standard WordPress install. It is used solely for the purpose to run custom functions on installation of WP and should be removed afterward. You can learn more about this file here.
https://wordpress.stackexchange.com/a/77641/59053
Whatever added this file, it can not be deleted, downloaded or have its permissions changed (at least thru a FTP program like Filezilla). These actions simply error, permission denied.
Now, it can be renamed. So that is what I did. I added
.old
to the filename. Now Connections was able to be activated. The other plugins should activate fine too, but I did not try as it did not seem necessary.Whatever this file is doing, it can not be much, judging based on its file size.
Hope this helps!
10/10/2018 at 9:09 pm #474612Michael Chuchro
ParticipantThanks for taking a look. I would have never figured that out. Much appreciated.
-
AuthorPosts
You must be logged in to reply to this topic.