At my current place of employment I've inherited a Drupal 6 site that I am maintaining and updating. There's a custom module that has some copy in it that needs to be updated.
Naturally, I went in and edited the .module file in my local environment, tested it and it looked great. We pushed the file to our development server and cleared the caches, theme registry etc and the change will not take place. It is still reading as the old copy.
As I've said, I've cleared the cache, deactivated/reactivated the module etc.. I've even tried to run update.php but the module in question doesn't actually appear in that list (there's no hook_update in this module it would seem). Is there some other trick to getting Drupal modules to register a change in the code?
One possibility is that the PHP process is not reading the new file but has the old one cached. You should restart your php-fpm or apache, depending which way you are running the site, to make sure the APC or Opcache are cleared as well.
I would also double check the content of the actual .module file to be extra certain that the new version is really there.
Yet another possibility that comes to mind is that you'll have to make sure you are updating the code in the correct location, ie you need to double check that the web server is serving Drupal from the location you are updating.
Related
I am working on SuiteCRM, and i want to change the CSS of my website in order to personalize it but there is an issue.
When i am changing the "style.css" of the SuiteP Theme, the pages aren't changing at all. Here is my question:
Does someone know how to change the css of this CRM and can help me to fix it ?
Thanks a lot
Make sure that your active theme is "SuiteP".
You need to know that SuiteCRM store things inside "cache" folder and you are doing changes without refreshing cache files. Cache files location will be cache/themes/SuiteP/css/style.css. So for quick changes, you can use browser developer tools.
Moreover, if you change core style.css then empty cache directory and (hard)refresh your browser. If cache files don't exist then Suite will build new using core file.
Like Star previously mentioned, Suite does cache the CSS.
Though, if you're not updating the SASS file, and just updating the CSS directly, your changes will be temporary for when the CRM next re-builds the CSS (I believe this is part of the Repair and Rebuild process in the admin section), your changes will be lost as the CSS file constructed from the style.scss file.
I'd recommend installing sass (via a gem or other means, however you choose), making changes to the scss then recompiling the css (or watching for changes if working locally, which I hope you are for working with Suite) when you've applied your changes.
If you still don't experience changes, try a repair and re-build or delete the cache directory and let it recompile on the next page load.
there are 2 options:
change core file and then delete cache contents. Refresh your page twice.
made changes in cache file. Make sure developer mood is off. Once you are done then copy it core file.
Create a new subfolder CUSTOM, copy the CSS files that are under suiteP (or the current theme) into the new custom. copy the whole path with folders, even if the folders are empty.
So the new path for the sytle.css with be /costum/theme/....../css/sytle.css
Change the file under the custom folder. The previous answers are not correct. This is well documented under the suite CRM docs.
Sometimes it doesn't work. Try next steps:
SuiteCRM better to use in development mode.
Not always the cache files deleting works for me. Better to use the tool in Admin panel - Quick Repair.
Sometimes good to clear browser cache (in dev mode reload a page by right clicking the refresh button).
I'm working on a Prestashop site and recently noticed about the SMARTY features (Menu: Advanced > Performance).
I realized that in order to show changes I made in the css, I must select one of the last two options (first one was selected by default).
Screenshot (I'm sorry the site is in Spanish)
1)Never recompile template files
2)Recompile templates when files are modified
3)Force compilation
My question is: when it comes to an online shop, wich option should I select until I finish editing the code? What's the difference between both?
It may take me a couple weeks to finish the job and I don't want to mess anything up.
Thank you guys.
When you're starting to dev onto the shop, whether it's front or back, you may have to choose the option to recompile when files are modified. I'm always choosing this option because it allows me to develop or debug some files and the server keeps serving cache files to the visitors.
Also you may have to edit the file defines.inc.php file in the config folder in order to define the _PS_MODE_DEV to true, for example like this :
/* Debug only */
if (!defined('_PS_MODE_DEV_'))
if (in_array($_SERVER['REMOTE_ADDR'], array('217.128.240.59')))
define('_PS_MODE_DEV_', true);
else
define('_PS_MODE_DEV_', false);
Doing this so you'll be able to get some logs when you're updating something. Placing your IP into the array keeps everyone safe from seeing the logs (notices for example).
In PS 1.6.
- Configure the SMARTY to "Recompile templates if the files have been updated" then deactivate the option "Smart cache for CSS"
- make the changes in your CSS files,
- delete the folders mentioned sadlyblue in comment.
- and activate again the "Smart cache for CSS" SAVE to recompile theme.
I have recently migrated a Magento website which had been using merge_css_files successfully. On the new server however I cannot get it to work and would very much appreciate any advice on the matter. The system will create the css files in media/css but they are always blank (unpopulated). I suspect that this might be something to do with the server itself as it worked previously on the old server.
I have already toggled Merge CSS on and off, flushed the caches multiple times, deleted the files from the media/css folder, updated all file and folder permissions, checked the ownership in ftp.
Perhaps you have experienced the same or could advise on a possible solution?
So, I have a strange issue with Drupal imagecache.
When I upload an image, the image is correctly stored in a folder, but imagecache doesn't generate the other cached images.
It doesn't work anymore after I moved the website from development server to the production environment.
The production server is IIS7.
All the "files" subfolder have both write/read permissions, imagecache module is supposed to create folders inside "files" folder.
The GD toolkit is correctly enabled (in Drupal report, imagecache module is correctly enabled). It is php 5.2.
thanks
Check out Imagecache's troubleshooting guide in the handbooks. In particular, check the logs for errors explaining where the process is breaking down.
Also, check the paths that are included in your pages and make sure they are still correct, now that you've moved the site to a production server. This issue has some more tips, specific to the path problem.
Finally, if none of that helps, check the issue queue. There are several issues related to IIS.
99% of the time when I have an issue with imagecache not creating images it has something to do with file system permissions. Verify that your web server is able to write to all of the files/imagecache directories recursively.
I have recently moved a drupal site. (both servers run on a debian based LAMP stack) Everything works great here, including the uploading of images via a CCK filefield. Original url:
dev.example.com/foo
Deploying it to a test folder on the production server to a test folder for an environmental shakedown cruise lead it here:
www.example.com/foo
Everything works here too, including image uploads. After adjusting sites/default/settings.php, then making it readonly again, I renamed the folder to its production name:
www.example.com/bar
Everything works fine here except for image uploading. I've adjusted the webroot variable within settings.php .
Things I have tried so far:
Gave php system user write permissions to sites/default/files (images are set to go in sites/default/files/images but imagecache just puts them in sites/default/files)
Enabled file php file uploading for www.example.com/bar/sites/default/files
Are there any other configuration settings I should be looking out for here? I'm running low on relevant solutions.
Edit: I had quite the typo there, I adjusted sites/default/settings.php, not sites/default.settings.php .
Your question is slightly confusingly framed. default.settings.php has no impact on Drupal -- its merely a template. The file that contains the actual database connection information and other configuration is settings.php.
You may also want to look at your .htaccess file in your root Drupal folder and try changing the RewriteBase directive to the folder you are accessing your site on. Usually you should not have to change the $base_url directive in the settings.php file that you may/may not have done. Reverse that change for now if you have (you may need to play around with that later though).
imagecache will always upload the image derivatives in sites/default/files but imagefield will upload the original image in the folder you specify (within sites/default/files). You will get a setting for the imagefield under Manage Fields->[Name of Image field]->Configure under Path Settings.
Please google to understand the difference between imagecache and imagefield. Make sure your sites/default/files (and subfolders) are writable by the apache user (usually www-data).
In such situations, its usually a good idea to pick up a book on apache (if you haven't already) and try to understand how it works. It will be time consuming but will help you out in the future when you encounter configuration issues like this.
This worked for me. When having issues uploading images to a cck field, I gave write permissions to directory:
sites/default/files/field/image