i am trying to update the core of drupal with drush on openshift by entering "drush up drupal" but im getting this error message
Directory /var/lib/openshift/[userid] exists, but is not writable.
Please check directory permissions.Unable to create backup directory
/var/lib/openshift/[userid]//drush-backups/drupal1.
ive tried
chmod +w /var/lib/openshift/[userid]
to make the directory writeable but i dont have the necessary permissions.
What is the best way to update drupal core on openshift if drush doesnt work?
Thanks for any info on that!
Try:
drush up drupal --no-backup
Related
Despite the complete installation of drupal 7.59, when I execute command drush cc all this message is displayed : No Drupal site found, only 'drush' cache was cleared., even I have installed a custom module in my site and I can work with my drupal site on localhost/my_site/ in browser, it's not recognaized as a Drupal site !!!
my main problem is that module is installed correctly but sql tables are not created in database and drush clear cache command doesn't help.
any one can help me what is wrong and why is this happening?
Thanks!
99% sure that path variable is wrong. Please check https://www.drupal.org/forum/support/post-installation/2014-05-14/drush-no-drupal-site-found-only-drush-cache-was-cleared
I'm not sure which OS you are using. Check path and port for mysql
I´m installing suiteCrm version 7.10.2, license agree works fine, system check works fine but when i´m done with the database and sdmin config and hit next don´t appen anything. I check the console and get the ReferenceError: YAHOO is not defined
I´m installing in my domain and not locally.
In chrome console i get this error
install.php:14 GET https://www.digitalinput.pt/SuiteCRM-7.10.2/cache/include/javascript/sugar_grp1_yui.js?s=6.5.25&c= 404 (Not Found)
but the file exists and i add a 777 permission just to try and nothing changes!
Check your .htaccess file. I can see you are using a subdirectory so make sure you have
rewriteBase /SuiteCRM-7.10.2
That should fix the 404.
you need to give the 'cache' folder write access (Recursively)
if you have access to ssh, you can run this commmand on you terminal :
Note : you need to be in the crm folder path
chmod 0777 -R cache/
then you refresh the page back
I have a drupal 7 site that I am trying to migrate to Pantheon. I have done this in the past by using the drush ard command to archive the site. I am trying to do this now and I am getting an error. It does create an archive file, but the file does not include any themes or custom modules. The command I am running is
drush ard --destination "./archive.tar.gz"
and the error I get is
Some site subdirectories are not valid Drupal sites: ./archive.tar.gz
[warning] Archive saved to C:\Users\sarah\Desktop\GrabABag/1
[ok] C:\Users\sarah\Desktop\GrabABag/1
It creates a file named 1 and if I use that in the migration it shows some content, but no theme and nothing from my custom modules. Any help would be appreciated!
The right command is:
drush ard --destination=./archive.tar.gz
I'm using CakePHP 2.0 RC-1. After checking out the project from SVN, the application is starting to complain that it can't write cache files to the tmp/cache directory. Since this is local, I know the directory is writeable and I can CLEARLY see that the directories are even filled with files, so the error is a bit strange.
Here are some of the errors I've encountered:
_cake_core_ cache was unable to write 'cake_dev_nb' to File cache
fopen(c:\cake\app\tmp\cache\models\cake_model_default_media) [function.fopen]: failed to open stream: No error [CORE\Cake\Cache\Engine\FileEngine.php, line 127]
No error?! Wth?
Now, if I look in the FileEngine file, at line 127 it reads:
if (!$handle = fopen($this->_File->getPathName(), 'c')) {
return false;
}
By replacing the "c" with "w", no error is encountered and everything works as it should. But, it should not be necessary to modify the core Cake libraries to work around this problem. Let me repeat that on my other computer this works as intended, without editing the core library. Both use the Windows OS and the read/write rights to the tmp/cache-folder is exactly the same.
Edit: Here's a site that experiences the error outputs I'm having locally
Example site found by Googling. Not my site: http://www.12h30.net/credit/
Any suggestions?
Update: Here is why: This is caused if you have a PHP-version that's too low, before 5.2.6, as outlined by "api55" in the comments. Thanks for the reply. Hope this helps you too.
Well, in my case, when I checked my app, it hadn't the /tmp folder. Then I created the structure (/tmp/cache/models, /tmp/cache/persistent) and all worked well. This happened to me maybe git ignore empty folders, so they weren't created.
I had a similar problem, it was because I had chown -R www to the app/tmp directory to get Cake to run "properly" without giving everyone write privileges. Looks like during development the only way to use the console and the web is to give everyone write privileges, or add yourself to the www group perhaps.
Easy solution:
chmod -R 777 app/tmp
or
chown -R username app/tmp
while using the console and
chown -R www app/tmp
when using the web
Just give the right CHMOD (776 works fine for me) to app/tmp
for windows users with the same error/warning: make sure you run the command prompt in elevated mode ;)
I'm trying to get bake working on my subdomain which is under shared hosting.
Is there a way we can get this working? I know how to connect to server via ssh shell but then what do I do after that?
First cd to the directory where the cake script is. On a Linux webserver, this would probably be something like ~/cake/console/, if you've put the CakePHP libs outside your web-accessible directories. If you've put everything into your web directory you'll probably have to go somewhere like ~/www/cake/console/.
Then simply type ./cake bake and take it from there.
You shouldn't have to do anything with environment variables. This is only necessary if you want to be able to run the cake console from any directory. I find it less of a hassle to just cd into the cake console's directory and run it using ./cake.
same as local machine cd <path_to_console> cake
if you do not know path_to_console ask for host support,
also path_to_console may be in environment path then just use cake in all dirs