I just updated to the latest OA release (2.17) and now the OA toolbar and some other elements only seem to display correctly in Chrome (but not in Firefox or Explorer).

This problem did not exist before the update (which was a fresh instal of OA 2.15).

Flushing web and local browser caches makes no difference.

I compared four browser engines using Avant, and have included screenshots below.

If you want to test this 'live' I have set up a 'development channel' for the site as I get things going:
http://praxishosting.net.au/development

Cheers,

H

Comments

hazit’s picture

Issue summary: View changes
dsnopek’s picture

I'm able to confirm the issues on http://praxishosting.net.au/development - but I can't reproduce this on any of my sites (also 2.17). At this moment I don't have any suggestions. :-/ Hopefully someone else will have some ideas!

hazit’s picture

Update: problems started with upgrade to 2.17, but sadly don't seem to go away with 2.18.

mpotter’s picture

Maybe try disabling the new advagg module? I cannot reproduce these problems on my sites either. But advagg does it's own caching that might be causing this.

hazit’s picture

Hi Mike - you are a legend.

Disabling the Advanced CSS/JS Aggregation module solved the problem.

However, the problem seems to re-appear when re-enabling the module - so technically the problem is still there.

I am very happy to have solved this problem, but there still seems to be issues with that module somehow.

Anyway, thanks again for your advice.

H

mpotter’s picture

When you enable the advagg module, go to its config page here: admin/config/development/performance/advagg

Click the Operations tab and try flushing the various caches there.

hazit’s picture

Status: Active » Closed (works as designed)

Hi Mike

You were right - this seemed to work - here's what I did:

  • go to admin/config/development/performance/advagg/operations;
  • at the bottom go to the 'Drastic Measures' heading, which include: Clear All Caches; Clear All Files; and Force new aggregates;
  • run each of these in sequence in descending order (running these in a different order or clearing other caches at the same time does not seem to work)

I'm closing this as even if its a bit temperamental, it seems to 'work as designed'.

Cheers and many thanks

H

hazit’s picture

Version: 7.x-2.17 » 7.x-2.19
Status: Closed (works as designed) » Active

Sorry to be a pain but flushing the caches using the steps above only works for one or two page loads, and then the toolbar problems return.

Disabling the advagg module fixes the toolbar problem, but brings with it the following intermittent error message:

Warning: file_get_contents(/jquery.ui.touch-punch.min.js) [function.file-get-contents]: failed to open stream: No such file or directory in drupal_build_js_cache() (line 4955 of includes/common.inc).

advagg and related modules seem to cause nothing but trouble for my instal. Clearly something is still looking for it and is unhappy that its no longer activated.

Is there a way of stopping this message from appearing?

These problems began with 2.17 and persist through 2.18 and now 2.19.

mpotter’s picture

The 2.19 version no longer enabled advagg by default. As you said, I think it's causing more trouble than good. It's still included as a module for sites that are sub-theming Radix and hitting the css selector limit in Internet Explorer. But that should be a small number of people.

Not sure why you get errors after disabling the module. Try actually uninstalling the module using:

drush pm-uninstall advagg

and then clear the drupal cache with

drush cc all

You might also delete any css and js files in your /files/advagg, /files/css, and /files js directories to force Drupal to rebuild all the caches.

hazit’s picture

Status: Active » Closed (works as designed)

Thanks Mike