I just installed the module "Date" and after enabling drupal gave me the error: Enable Date API first, so i enabled the Date API and then the Date module and now drupal crashed and it says "Page not found" and i dont have any menu in the admin panel.
Menu rebuild does not work, i created an script for it without result
Restore from your most recent backup which you should have made before installing a new module. ( Note:Drupal is not for amateurs, despite what they say. Drupal does not have professional governance, like say Wordpress, and that makes it relatively demanding for the inexperienced. With Drupal you really need to be sit next to a helpful pro for a year.)
Check that the version of PHP , Drupal, MySQL and the Date module are all compatible. This is work, BTW. If not compatible, then reinstall where necessary and cross your fingers.
Check for known issues by Googling something like or based on "Drupal 7 Date module". Drupal 7 is old and issues that have arisen with so-called compatible modules may be well-documented.
I fixed it by restoring my sql backup. Not a good fix but yea...
Related
I installed latest open social 11.7.0 distribution for Drupal 9 using composer. Smoothly and setup went fine.
However when updating using composer update it takes ages to finally cast a killed message. Output is not really verbose and I don't have a clue what happens behind the scene. I saw it could be "memory usage" related but bypassing memory limit usage ends in same result.
To be mentioned I have an other classic drupal website on same server and composer update runs like a charm.
Any advice or idea ?
Thx beforehand,
I am quite the newbie as far as Drupal dev goes. I've been asked to upgrade the core version of an existing website.
I used composer to update the drupal/core package and its dependencies, cleaned the cache, ran the database updates, which went rather smoothly...BUT...
Some of the blocks are not displayed anymore
Autocompletion in fields does not work anymore
My drop-down selects are not displayed (the values they are using are loaded properly)
I have no idea why this happens.
Any hint, anyone?
Thanks!
I've been floating around the Google and everything's getting more confusing now. What i want to know is how to install Memcache or Memcached. Even which one to install, i'm still not sure. It is super confusing.
I'm on Redhat RHEL. Actually i have installed Memcached (with 'd`) on my Web Server. Then according to the articles, i enabled Php Extension, etc. Then what is supposed to happen? Totally no improvement in performance.
Then i feel thats not enough and i googled again. Some say to install on MySQL Server. So what about PHP Extension and Drupal Module which are supposed to be configured, if i install it on MySQL Server? I'm really not getting it.
So i have Drupal 7 and please let me know in simple way for which is the right one to follow :(
Memcache or Memcached ? (Why this two so confusing?)
Where to put at?
Does it really need Drupal Module to work?
Please simply give me a straight dummy guide :(
"Memcache vs Memcached" - first one is a module (extension), second one is the daemon. See "Memcache Vs. Memcached" for full explanation
"Where to put at?" - you said you had it already installed on your server, it should be installed easily with some package manager e.g.:
pecl install memcache
"Does it really need Drupal Module to work?" - Yes, Drupal needs to know that you want to use memcache. The Drupal module will move cache, sessions and lock tables into memory (see https://drupal.org/project/memcache).
To make memcache module work, you need to put the following into settings.php (change you module path respectively):
# Memcache
$conf['cache_backends'][] = 'sites/all/modules/contrib/memcache/memcache.inc';
$conf['cache_default_class'] = 'MemCacheDrupal';
To see whether it works, go to "admin/config/system/memcache" (this is Drupal 7 path) and turn on "Show memcache statistics at the bottom of each page" - if everything works well, you should see something similar at the bottom of the page:
OPERATION BIN KEY HIT
get cache_bootstrap cache_bootstrap-variables 1
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.
Last week I had released a version of a WordPress plugin that works if the user was doing a fresh install, however if they already had the plugin and upgraded it using the WordPress upgrade automatically feature, problems occurred and some of the database elements were erased. So I had to revert back immediately.
I was wondering if there was a way to test the plugin through the upgrade automatically functionality before hand instead of having to release it and hoping you get it right the first time.
I would set up a dev/local site running the previous version of your plugin. Then, copy over the latest changes (overwriting all of the files) and test things out.
In essence, that is the same thing that happens during an automated upgrade.