Cannot install/uninstall Drupal 7 module - drupal

I'm trying to install a modified version of the Rules HTTP Client module. But the problem is that I cannot install this because when I try to it tells me that "Rules HTTP Client" already installed.
So I tried to disable and uninstall the module first. I disabled it but then it is not listed in the uninstall tab.
I do not have access to the server on which the Drupal site is hosted so everything I do has to be through the admin dashboard on the site.
Previously I could just install a module and it would override the already installed module. Is there a way to uninstall this Rules HTTP Client module? And does anyone know why when disabled it does not show in the uninstall tab?

If the non-modified version doesn't appear in the uninstall tab, that's because it is already uninstalled or marked as uninstalled in database (you can check the schema_version in the system table, set to -1 means uninstalled).
However, the previous sources are probably still there and the former .info file in this case need to be removed or at least commented out depending on how you can access the server.

Related

To what extent can MAMP be hacked?

I am running Wordpress on a local development server to test plugins from 'dubious' sources. I believe I've been hacked after installing an unofficial copy of a plugin. Now I'm looking for help to assess how serious this may be and how to proceed.
Here's what exactly went down:
Installed MAMP (4.2) on my Mac (10.14.6), with htdocs in it's default location (in the MAMP application folder)
Installed multiple Wordpress sites to develop for clients over several months
Used one of these existing, old, dev sites to test plugins before purchase
I began to install a plugin .zip file, however after I clicked "activate" I was asked by macos whether to allow MAMP access to photos, and then to calendar, both of which I denied. The activation failed due to a "Fatal Error".
I ditched this plugin and moved onto the next. The next one also failed due to fatal error, this time with the error message: "Fatal error: Namespace declaration statement has to be the very first statement or after any declare call in the script in"
Googled this message revealing it's common when hacked.
So, does the hacker have any access to this website? To the entire local server? To my entire computer where MAMP is installed?
Am I in the clear just deleting the plugin? Clean install MAMP?
Thanks.
Wordpress hacks tend to be more about collecting information from WordPress.
Anytime you get a warning like that, it should tell you where the issue is.
However, I would install Wordfence on your local sites and have it run a scan. It will compare core files etc to what is on the repo and tell you. It will get about 99% of it unless it is a Zero day.

Setting up wordpress on Ubuntu 12.04

I have dual-booted my Win7 laptop with Ubuntu 12.04, and I'm trying to install Wordpress. I have installed Apache2, Mysql-Server, and Wordpress and I keep getting asked for ftp credentials when I try and install plugins/themes. I know how to install the themes etc. manually by downloading and unzipping into the correct folders, but this isn't a permanent solution.
I've tried uninstalling and reinstalling everything but I keep getting faced with tutorials on setting up virtual hosts and I'm not sure if I need to have one?
Can anyone point me to an easy to follow (for beginners) tutorial from scratch? Or tell me if I'm missing something?
My Wordpress site needs to be moved from local machine to a server when it's finished (I don't know the server yet so I can't just start using it) so I need it to be as easy to use as possible.
Yes, there are available tutorials for that.
Step 1-
Installing the server-
Installing the server
Initial Setup (Optional)
Step 2-
Installing Wordpress-
https://www.digitalocean.com/community/tutorials/how-to-install-wordpress-on-ubuntu-14-04

Msi installer stopped working

I previously installed a website on the server by running an msi package and everything worked fine. Now, when I try to run the same msi file (to Repair/Uninstall), I get a message:
When I click Cancel, I get the following message:
Anybody has an idea what happened and how it can be fixed?
I would recommend that you run the MSI with logging enabled. This can be done by using the /l*v C:\mylog.txt switch or by modifying the registry. The log will provide you with more precise information as to what is going wrong during the msi process.
The articles below describe how to enable logging and the logging process in more detail
http://support.microsoft.com/kb/223300
http://technet.microsoft.com/en-us/library/cc759262(v=WS.10).aspx
http://msdn.microsoft.com/en-us/library/aa372847(v=vs.85).aspx
Once you have the log you can use a set of MSI tools like the Orca installer database editor tool on the Windows SDK to correct any issues.
This is the link for Windows 7 SDK which contains the msi tools.
http://www.microsoft.com/en-us/download/details.aspx?id=8279
Sorry for answering my own question, but I found the problem and I want to share the solution:
After I installed the old version on the server, I changed the name of the msi file. Consequently, I could not run the old version to repair/update. I could not even install a newer version over the old version, as the installer needed the old msi to uninstall the old version.
When I changed back the filename of the old version, it allowed me to install the new version.
CONCLUSION: Don't change the name of the msi file after installation.

Is There A Way To Install Unstable Version of Plugin via Built-in Plugin Installer

I'm wondering if there is a way to install an unstable version of a published plugin.
Let's say I updated my plugin version 1.0 to 1.1.
Then I put Stable tag: 1.0 in the readme.txt file so that everyone downloads the stable version v1.0.
Now my question is that if I want to test the unstable version on one of the remote servers, isn't it possible to install v1.1 with the built-in plugin installer?
I'm currently doing this way:
deactivate the old version
delete the plugin
upload the unstable version
activate it.
If the updating process could be shorten this way, it would really save my time.
search and find the plugin name to install in the Add New page.
click on the unstable version link.
Thanks for your information.
I'm not sure that this is the answer you are looking for but...
I was running into the same issue and instead what I have chosen to do is actually edit my plug-in on a "test-bed" site. I have a site that I test all of my modifications on before publishing and I access the files directly via FileZilla FTP Client.
This allows me to take the most up to date file from the server, edit it on my machine (using Notepad++) and upload the change to the server for testing. If it breaks the site in some way I can always re-upload the original via FTP and everything is back online.
Hope this helps!

Call to undefined function field_attach_load() in my-path-to-root/my-site/includes/entity.inc on line 320

I am moving a site over to a different server to test.
getting this error
Call to undefined function field_attach_load() in my-path-to-root/my-site/includes/entity.inc on line 320
strange... if i try accessing a subdirectry http://www.mysite/randomstuff
i get this error
Fatal error: Call to undefined function user_access() in /home/borsodas3/digipowers.devserver2012.com/modules/overlay/overlay.module on line 130
Fatal error: Call to undefined function node_access_needs_rebuild() in /home/borsodas3/digipowers.devserver2012.com/sites/all/modules/taxonomy_access/taxonomy>_access.module on line 598
here are the two php.info files
going to this server [http://www.freeenergymedia.com/phpinfo-to.htm][1]
from this one [http://www.freeenergymedia.com/phpinfo-from.htm][2]
the drupal status report from the site I am migrating FROM looks like this...
Info
Drupal 7.8
OK
Access to update.php Protected
Error
CTools CSS Cache Unable to create
The CTools CSS cache directory, ctools/css could not be created due to a misconfigured files directory. Please ensure that the files directory is correctly configured and that the webserver has permission to create directories.
OK
Configuration file Protected
OK
Credit card encryption Credit card data is encrypted during checkout for maximum security.
OK
Cron maintenance tasks Last run 26 min ago
You can run cron manually.
To run cron from outside the site, go to mysite.com
OK
Database system MySQL, MariaDB, or equivalent
OK
Database system version 5.1.57-log
OK
Database updates Up to date
OK
Date API System date settings
The timezone has been set to America/New_York. The first day of the week has been set to Monday. The medium date format has been set to to F j, Y - g:ia.
Error
Drupal core update status Not secure! (version 7.12 available)
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.
OK
File system Writable (public download method)
OK
Fitvids library Installed
Fitvids Javascript Library. Download it from here, copy it to the module directory, and rename it to jquery.fitvids.js.
OK
GD library PNG support bundled (2.0.34 compatible)
OK
GD library rotate and desaturate effects bundled (2.0.34 compatible)
OK
Images Product image support has been automatically configured by Ubercart.
Error
Module and theme update status Not secure!
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.
OK
Node Access Permissions 1832 permissions in use
If the site is experiencing problems with permissions to content, you may have to rebuild the permissions cache. Rebuilding will remove all privileges to content and replace them with permissions based on the current modules and settings. Rebuilding may take some time if there is a lot of content or complex permission settings. After rebuilding has completed, content will automatically use the new permissions. Rebuild permissions
OK
PHP 5.3.2 (more information)
OK
PHP extensions Enabled
OK
PHP memory limit 300M
OK
PHP register globals Disabled
Warning
Unicode library Standard PHP
Operations on Unicode strings are emulated on a best-effort basis. Install the PHP mbstring extension for improved Unicode support.
OK
Update notifications Enabled
Info
Upload progress Not enabled
Your server is capable of displaying file upload progress through APC, but it is not enabled. Add apc.rfc1867 = 1 to your php.ini configuration. Alternatively, it is recommended to use PECL uploadprogress, which supports more than one simultaneous upload.
OK
Web server Apache/2.2.3 (CentOS)
OK
cURL Enabled
The first thing I'd do is update to the latest version of Drupal Core. The error message you are seeing is coming from core, but could be from a contrib module. Update all your modules if any are as outdated as your Drupal core is. There are security issues in Drupal 7.8 and other issues which might affect your situation could well have been resolved. The current version of Drupal is 7.12 and a lot has been fixed since Drupal 7.8, which was released about 6 months ago, so you definitely want to upgrade core. Is it also possible that you are running different versions of core on the different machines? If so, the database might not be compatible, especially if you are taking a newer database (more recent modules and core) and loading it into a system with older modules/core.
After also updating other contrib modules and running update.php at appropriate times, if your problem still persists, you might want to use the "divide and conquer" method to identify which module is actually responsible. Remove groups of contrib modules and see where the problem disappears, then narrow it down to which one is causing the problem. It could also be a compatibility issue or configuration problem. Or you might have modules where the code has been updated, but update.php hasn't been run so the database isn't what it should be. You can also use tools such as the Devel module to try to track down issues, but it depends on how "broken" your site is. If you are getting "fatal errors", then you might first want to see what you can do to get past that.
I also notice you need to properly set the permissions/ownership of your files directory so that CSS caching can take place (among other tasks the webserver may be trying to do and which could also be involved in errors you are experiencing), even if not at the root of the "fatal errors".
Hope that helps someā€¦ troubleshooting can be a pain sometimes.
When I installed for the first time, I hadn`t checked "Create new database" and had the same bag but in line 321.

Resources