I logged in to the company's Drupal (7.19) site and noticed a lot of recommended updates.
There is a security update available for your version of Drupal. To ensure the security of your server, you should update immediately!
See the available updates page for more information and to install your missing updates.
There are security updates available for one or more of your modules or themes. To ensure the security of your server, you should update immediately!
See the available updates page for more information and to install your missing updates.
I chose to download the updates. I then proceeded to update, Drupal suggested I'd do this in maintenance mode.
Upon proceeding I was greeted by a long message, telling me that all updates had failed because the directories could not be removed.
nodeaccesskeys
Error installing / updating
File Transfer failed, reason: Cannot remove directory
Your modules have been downloaded and updated.
Run database updates
When visiting:
admin/config/development/maintenance
the box that says “Put site into maintenance mode” is not checked, yet the site still remains in maintenance mode when I visit it in another browser (so that I’m not viewing it while being logged in as the administrator.)
I feel both things are related seeing as I had no issues before I tried to update the modules in question.
I'm not entirely sure what to do here. Is there a way to fix this preferably without resorting to code? I'm not too familiar with Drupal. I just wanted to update out of date modules.
At this point I don't really care about not being able to update, I'd just like the site to not be in maintenance mode anymore.
Thanks in advance.
You might need to clear the cache on /admin/config/development/performance
Related
I would like to know when Drupal clears the cache (or rebuilds it in more recent versions of Drupal). Does anyone know how I can get Drupal to record an entry in a log, whenever it clears the cache? At the risk of sounding like a complete idiot, does Drupal use Drush to rebuild the cache when it does it by itself (on schedule)? Or, is Drush just for the dumb human to use?
As a first step, try using hook_cache_flush or hook_rebuild in a custom module and check the results.
As far as I know any rebuild/cache clear will go through these hooks.
I installed reCaptcha in the Drupal 7 module in hopes that it would work on the contact form, but it never did. So I did a really dumb thing and deleted the reCaptcha from Google and forgetting that connection to it was in the module.
It turns out that the reCaptcha did work but only on the admin login screen. Now that I am locked out, does anyone have a really brilliant idea for someone who made a really bad move?
I finally found the answer and I want to post it in case anyone else runs into a problem with any module in Drupal, not just with reCaptcha.
The main steps I used were found on this website: Disabling or enabling a module
All I did was make a backup of the db. Determined what the module name was that I was needing to disable:
SELECT name,status FROM system WHERE type='module' AND status='1'
Then change the status to '0' using of the actual module name I needed to disable:
UPDATE system SET status='0' WHERE name='module_name'
At this point I thought it was done, but because Drupal keeps a cached copy of it enabled in the db you still have to delete the cache:
DELETE FROM cache_bootstrap WHERE cid='system_list'
I have been developing this website and we had to use Gravity Form plugin.
There was a time when it went very vulnerable and the website was attacked (a massive crash occurred to the site) ever since the website has never been normal every again. It is extremely slow to download sometimes there are some error messages 503 We have securely monitoring the website, have the wordpress and every plugin updated to the latest version or even delete the one without the recent updates but it seems not enough because if you access the website now you will feel that it's extremely slow.
Is there anybody who has experienced this kind of attacked? (especially, from when you got attacked via Gravity Form plugin)
I would really appreciate you answer.
Scott
As Ed Cottrell mentioned you must rebuild your site.
Make a backup of files and database
Write down which plugins you use
Delete everything (leave only wp-content/uploads)
Install clean WP - it will be best if you use the same version you used
Install all the plugins - the data is still in DB, so you won't have configure them again
If you bought a theme - just download it again and install it. If someone made it for you - check it for some strange eval or some js files you dont's know. When you are sure it's clean put it back on the server.
When everything is done, change user passwords and ftp password.
Use https://wordpress.org/plugins/gotmls/ - it will help to find some nasty code.
I can't update all the add ons that I have installed, everytime I click that "update plugins" button, I got this error message: "Unable to locate this add-on on concrete5.org" on every plugins that i want to update
At first, I developed the website on my localhost. I connect it to the marketplace from there, so the URL of the project is something like this: locahost/myConcrete5Web,... in the middle of the development, I moved it to a development server. I'm not so sure if the problem appear on this server or not, cause I don't test the update functionality in here. By the way, when googling for the solution of my problem, I found the similarity of the case on this thread (http://www.concrete5.org/community/forums/chat/marketplace-is-broken-on-upgrade-to-5.5/) with the one I have right now. So, just FYI, I do update the concrete5 version on this development server. From 5.5 to 5.6
My client start found the problem on the staging server. He tried to update the plugins and got that error message that I mentioned earlier. He told me and I started to google out for the solution. I found several clue from these pages:
http://www.concrete5.org/community/forums/chat/marketplace-is-broke...
http://www.concrete5.org/documentation/how-tos/editors/cant-connect...
http://www.concrete5.org/community/forums/installation/how-to-disco...
So, I tried to disconnect my website on the staging server by removing the value of MARKETPLACE_SITE_TOKEN & MARKETPLACE_SITE_URL_TOKEN on the database. Nothing changed. Next, I tried to delete the project listed on my concrete5 marketplace account. Turns out the problem getting worse. My concrete5 installatation still says that it is connected to the marketplace. They still show the project URL of the one that I have deleted before.
Now, I have no project listed on my account, when I tried to reconnect to the marketplace, it's show that i have successfully connect my web to concrete5 marketplace with the same project URL that I have deleted before. yet there's still no project listed on my account. Now, regarding the paid add ons, I'm kinda confused right now, where does my paid add on license go with this condition?? Do I still have it?
Anybody know how to resolve this problem?
Please feel free to ask for more clarification, my english is bad and I don't think my message could be understood well enough
Not really sure if this is the correct place to post question like this. I've posted this on concrete5's forum with no response at all. I think this is the kind of issue that should be complained to the concrete5 team. The fault seems to be on how their marketplace work. But unfortunately, AFAIK, they don't give such technical support/bug report for this. So, I hope stackoverflow could help me out.
My client has 1000 WordPress blogs hosted on a server for customers. Each one is in its own domain through cpanel and SuPHP, running in CGI mode on Apache2.2. Now he wants me (I'm the PHP programmer) to get WP-Cache loaded out on each of these blogs and not just activated, but enabled. He also wants the timeout value set to 2 days instead of the default setting.
I have root on LAMP.
What is the preferred way to roll out an update to each blog such that on a page view, it sees if WP-Cache is enabled or not. If not, it needs to copy it out from a central source, activate it, and then enable it along with the different timeout value being used.
A way, maybe not the best way, is to write a script to copy the wp-cache plugin to every wp-content/pulugins folder. Then run another script that will go and modify every DB entry for it enabling it.
If not done correctly this can be devastating as it hits customer db's.
However, one thing to note is wp-cache has a history of killing other plugins. So, if you go in and add this plugin to everyone's wordpress it might hurt there experience if it hurts another plugin they have installed thus increasing support costs as people might be emailing trying to figure out what broke.
I take it this is being done to work on performance issues. Is it possible to maybe do some type of server caching outside of wordpress?
edit: after reading Joes comment I concur with him. Didn't even cross my mind.