Is there a problem with the Drupal 7 server or caching? Do not update CSS changes

Question

So my Drupal site does not reflect any CSS changes that I make. I tried to make a hard cache of the site, I tried several browsers, I checked the actual stylesheet on the server to make sure that it copies (the stylesheet reflects the changes, but the actual site does not work). Of course, I went to the clear cache section under configuration / performance in the admin panel. I switched to FTP and manually deleted the cache. I cleared the cache of my own browsers. CSS files go in the correct folder (I checked this too!). I literally did everything I could think of. I tried turning on and off aggregation and compressing the css options, clearing the cache between them. I checked the page source and it is certainly still present with old CSS.

Each debugging attempt led me to think that this is due to the fact that DNS is not refreshing. I read somewhere that someone made some changes to the Name Record. I set TTL to 1/2 hour, reset A Name Record manually, and just in case, I deleted the forwarding that I had in the domain.

This is what I did. People, what am I missing? I was looking for a network to solve, and no one who did not have this problem found a solution. Has anyone had this problem and fixed it? What did you do? Any ideas?

:: edit :: I just wanted to add that I use Skeleton Theme as a base.

:: edit edit :: I also used Devel to recreate topic registries.

Answer 1

Make sure the .info file name is exactly the same as the themes directory in sites/all/themes/

If not, the theme appeared for me, but the .info file did not affect.

Changed as one and the same, and it was embarrassed to see several topics available under the guise of a site, one for each .info file. I activated another topic and saw the changes. Just specify the directory and .info file in exactly the same way.

And of course clear the cache, disable ccs aggregation.

Answer 2

It was a cross-reference to the distribution queue, but I don't think it has anything to do with the Community Media Starter Kit distribution itself.

First, you must exclude DNS by setting DNS locally and / or flushing the DNS cache. These are steps for OSX, but you can find similar instructions for any OS ...

Clearing the local DNS cache

Mac OSX Lion DNS Search Order

Once you have determined that the site you are running ftp'ing on is the same site, let's see how the themes are downloaded by the distribution. With any Drupal distribution / installation profile, you can redefine any module or topic included in the / [PROFILENAME] / modules or profiles / [PROFILENAME] / themes profiles by posting a new / old / modified version on sites / all / modules or sites / all /themes. When you move modules using the Drupal registry, you get a WSOD. This often requires the use of drush rr or manually clearing the cache tables] 1 , since the WSOD will stop all pages from loading, including Admin> Performance> Clear cache. This is REALLY unlikely to be required for the topic.

In this particular distribution, you can also use the CSS Injector module to change CSS without having to update the css files themselves. This css is stored in the database, so it will affect the site you are looking at.

Answer 3

I have never used the basic Skeleton theme, but Omega has theme settings in the Appearance section, where you can enable and disable styles for each theme. Maybe the Skeleton has the same thing?

Answer 4

I am just starting out at Drupal, so I can be fully tracking my answer, but I will still tell you what I have experienced in recent days. So I installed Drupal Commerce Kickstart and made a kids theme for kickstart. I installed it. And when I changed its CSS and downloaded it through the ftp client, it took more than half an hour before the change took effect. So I searched and, finally, with Firebug, I found out that Drupal makes its own CSS and places it in the / default / files / css sites. When I looked with the Inspector in which css file I needed to make the changes that I wanted, it took several seconds after the modified css file was reloaded on the sites / default / files / css for the changes to occur. Thus, it is obvious that these are css files before the css files of the topic. Which for me I found stupid. I do not know if this will help you. In any case, I was wondering if it is really necessary to create these files on the sites / default / files / css. I deleted them for testing, but they returned. I do not know if there is an opportunity to stop this process.

Answer 5

Pagespeed (site caching system) from whois hosting was the reason for this for me. I logged into the client’s hosting account and disconnected it. The problem was solved, but I also implemented this code, which allowed me to restore the theme registry every time the page was loaded, and this was of great importance. Now css changes instantly. Before the site starts, I will disable this code.

Are you sure you are not going to rebuild the registry so?

To rebuild the theme registry and the .info file during development, add this to your theme template.php file:

 <?php /** * Auto-rebuild the theme registry during theme development. */ if (theme_get_setting('rebuild_registry') && !defined('MAINTENANCE_MODE')) { // Rebuild .info data. system_rebuild_theme_data(); // Rebuild theme registry. drupal_theme_rebuild(); } ?> 

And add this to your theme-settings.php theme in your {element_name} function _form_system_theme_settings_alter (& $ form, $ form_state):

 <?php $form['rebuild_registry'] = array( '#type' => 'checkbox', '#title' => t('Rebuild theme registry on every page.'), '#default_value' => theme_get_setting('rebuild_registry'), '#description' => t('During theme development, it can be very useful to continuously <a href="!link">rebuild the theme registry</a>. WARNING: this is a huge performance penalty and must be turned off on production websites.', array('!link' => 'http://drupal.org/node/173880#theme-registry')), ); ?>