This is my first attempt at using drupal and I am trying to add a module to my drupal page. I keep on getting this error when i try and install anything...
Does anyone have any ideas? Any help would be much appreciated, thanks!
For those that stumble upon this in the future...
#Hardy was right with his first comment:
Check your installation folder rights.. modules are in folder sites/all/modules and that should be writable (at least if you are just testing it locally). To add module you can just download that module as zip from drupal.org and extract it to sites/all/modules then go to "modules" page in drupal admin panel and activate that module.
and
Actually i have always installed modules "by hand" and that has been ok for me. But maby this helps you to get right permissions: drupal.org/node/244924
I ended up just doing what he suggested (doing it manually) and it really was no big deal...
Also, here is the link that he provided: https://drupal.org/node/244924
Related
I am a newbie using TortoiseSVN and I have created a basic plugin in the WordPress directory but I want to just update the description page (readme file) but couldn't do so.
The following are my steps:
Make changes to the readme file on my local computer.
Right-click on the readme file and select 'SVN Commit' (No errors, but this won't update the official plugin page hosted over at WordPress directory).
Right-click on trunk folder then select 'Branch/tag', point to existing tags/1.4 but the error says that the file exists...
May I know which step I have done wrong?
I have viewed the following thread but still couldn't find the solution myself...
Reference: https://wordpress.stackexchange.com/questions/301078/how-to-update-wordpress-plugin-readme-txt-description-page-without-triggering-a
I would appreciate any help from someone, thank you!
This is not really question, more an answer...
I recently updated Joomla to version: 3.4.8 and after that the Global configuration page was missing the CSS-styling.
I quickly tried solving it and came across alot of similar cases from searching Google... Some had "answers", but not and easy fix..So if anyone else is stuck with this problem, here is the solution :)
Run your FTP and locate the folder name "libraries" in your Joomla install on your server.
Then take a backup of this "Just in case".
Delete this folder and replace it width the same folder from a fresh Joomla install.
Some of the files in that folder was causing the issue, and if don't bother finder the specific file, then just do the above and the problem is solve.
Hope this helps someone :D
Run your FTP and locate the folder name "libraries" in your Joomla install on your server.
Then take a backup of this "Just in case".
Delete this folder and replace it width the same folder from a fresh Joomla install.
Some of the files in that folder was causing the issue, and if don't bother finder the specific file, then just do the above and the problem is solve.
Hope this helps someone :D
So basically you were hacked. Simply replacing the libraries and includes folder is enough to get your site online again, however it is not the solution. You need a complete security audit and review conducted.
Many hacks for Joomla install dodgy session or cache handlers - as a hook for them - and this can and will create an issue when loading the Configuration page.
Also if you are on a mac and you upload dot underscore ._ files to some parts of the libraries folder you can again kill the configuration page as Joomla is stupid and includes all the files in the folder irrespective of filename (actually a security issue in itself, but been that way for ages)
I've been trying to uninstall a magento plugin I've recently installed to reinstall it using Magento Connect. The log said that the plugin uninstalled successfully and if I go to the admin panel, the plugin's no longer there but when I went back to Magento Connect, the plugin is still listed there so I can't reinstall. Why is this happening?
Based on the answers, what I've tried so far are:
Clear cache through Admin Panel
Removed wordpress entry in core_resource
I've made sure wordpress xml in etc/modules is removed
I've made sure Fishpig folder in app/code/community is removed
Cleared cache in var/cache
Cleared cache in downloader/cache
Checked if there's xml for wordpress in var/package (there was none)
Reindexed magento
And none of this worked. The wordpress extension was still listed as installed in Magento Connect. I've been trying to uninstall repeatedly but it just won't go away even though the log said that the uninstall process completed. I've also tried reinstalling and upgrading. No success.
to remove the extension:
remove all the modules files, includeing the file which enables the module:
app/etc/modules/COMPANY_MODULE.xml
also make sure the entry is gone from the database by removing the correct entry in table:
core_resource
then refresh the magento cache
It should then disappear from connect.
Which module have you installed? Can you give me name so I can give you solution if possible for me. If module add new own tables in db then dont delete any module file otherwise may be magento crash. Its better way to uninstall from magento connect manages.
Clear the .cache folder in the downloader directory, in addition there is also another area where an xml can be present in var/package/
The package files are from magento connect so delete from here and have another check!
delete all files in var/cache/ and double check you are actually working in the right folder! if you have another caching system then clear it.
To delete the extension from Magento Connect (I believe you have already uninstalled it from Magento) you will need to delete the file var/package/Fishpig_Wordpress_Integration_{{version}}.xml
Thank you very much for all your help and time. I really appreciate it. I've managed to solve the problem. It's apparently a problem with permissions. I didn't realize soon enough that the permission for all folders had to be 777. I had most folders set to 777 except for 2 files on my etc folder (local and locals.xml) because of security issues. But after getting a go signal changing said permissions, I managed to uninstall the plugin and reinstall it. Now the Wordpress is fully integrated in the website with no problems and I've also returned the permissions for local and locals.xml back to it's original. Thanks again a lot for all your time.
I have a new installation of drupal 6.22 and one of the first things I did was to install CCK. Enabling this module gave me a WSOD on the whole site, so I deleted the module directory from sites/all/modules. This got rid of the WSOD but now whenever I enable a non-core module, the front-end of the site continues to work but the admin screen give me a wsod. I have read the drupal docs on this and installed dtools. With dtools on, I can see I'm getting the error
ERROR: Callback: system_main_admin_page() doesn't exist!
I am guessing that deleting the CCK files without disabling the module (CCK) may be part of the problem. How do I programmatically disable modules? Any other ideas on fixing this?
Thanks,
If you have basically a fresh install, it wouldn't be difficult to just reinstall Drupal which should solve your problem. If you don't wish to do that, you can disable modules in the database through phpMyAdmin, a DB query etc.
If in phpMyAdmin, go to the system table, find the module(s) you want to disable and change the status from 1 to 0.
I have posted on the template creator's site, as well as Magento support, but no one has responded.
The CSS is not loading at all on the custom theme I have installed, which is supposedly compatible with the current version of Magento.
You can view the page here: shop.dearearth.net
This is a fresh installation of Magento and the theme, with a fresh database.
I have a feeling it should be a relatively quick fix.
Thanks for looking.
All the links in your page referring to the
http://www.shop.dearearth.net/skin/frontend/base/
directory on your site returns 404. Make sure your css files are in fact in there. Also make sure your links aren't being broken by a .htaccess file.
Make sure your CSS is 777 rights by admin.
OR
Please copy the whole code from latest css and take it as a backup and create a new css file as same name and past the code.
Check in admin back-end, System > Configuration > General/Design if your theme is right specified. Also check if after you installed the new theme, the files have the proper rights (normally, they must be accessible by the web server with Write permissions)
For more info please also take a look at Magento Designers Guide for understanding of how Magento read and split template information. Maybe you have put the CSS and images in a wrong directory :)
Solved.. sort of. The version of the template turned out to be quite outdated, and the incompatible with the current version of Magento, which handles things differently in terms of calling styles in the page.xml file.
Thanks for your inputs.