Still on Drupal 7? Security support for Drupal 7 ended on 5 January 2025. Please visit our Drupal 7 End of Life resources page to review all of your options.
I am trying to install Drupal 7.9 on my hosting :
PHP 5.2.6
MySQL 5.0.24a
PDO enabled
But it get this error during the installation, on Database confirguation page :
Failed to connect to your database server. The server reports the following message: SQLSTATE[42000]: Syntax error or access violation: 1231 Variable 'sql_mode' can't be set to the value of 'NO_AUTO_CREATE_USER'.
Is there a way to access/display a drupal article without the site (like footer, menues, header, etc...) around it?
For examply to embed/display only the article itself in an iframe.
I want to integrate CometChat in Drupal7.
But cometchat uses sesid stored in Session table to get the information of currently logged in user.
This sesid is stored in cokkie and cometchat need to get this sessid from cookie and matches it with
the session table's sid.
I want to know how the 'key' part of this cookie is generated to store to store the sesid so that
cometchat can fetch this sesid from the cookie.
I understand from my hosting provider I have a 60MB php_value memory_limit. What elements of Drupal use that up and how can I optimise my deployment to free up memory ?
Also what other applciations and content type use PHP memory ? I am a Newbie I dont understand what PHP memory is?
In my company there are several Drupal-based project, on which developers are working.
I, as an administrator, was asked to find out how to improve development workflow.
Currently it looks as follows:
1. Developers are working on their local dev-machines, where Drupal instance is present.
2. When they make some changes which can go to test server, the commit them to svn repository and I am updating files on test server.
3. Client, after reviewing test version can accept them - changes needs to be made on production server.
In my opinion above workflow is not good when developers needs to make changes in backend by clicking. All of you know, that those changes are made in database, not in files (mostly I think). Sometimes we had situation, that during our development (dev-machines, test server) our client is making changes on production server (adding posts, sites, changing content, etc.). After that I have too much work to sync production version with test version.
What is more, when developer is making changes in backend, he/she needs to repeat those steps also on test server and on production server. This consumes a lot of his/her time , I believe, that it can be done in better way. Unfortunately I have foggy idea how to improve our work flow.