Feed aggregator

Hi all,

So who's making the trip to Copenhagen for Drupalcon?

I'll be there, and I'll be in Copenhagen and surrounds for the previous week on holidays too.

I haven't booked any accommodation for Monday to Friday just yet.
Is anybody looking to share an apartment or a large hostel room even.
This place
http://www.danhostelcopenhagen.dk
is literally across the road from the conference venue.

Regards
Alan

Hi Folks,
Anybody migrated Drupal 6.17 from an Apache box to a Zeus web server box. I have a Drupal site sitting in www.mysite.ie/cms working fine but ISP (Register365) is terminating the service. I did a MySql export and imported up to to the new box. Then I FTPed the original Drupal cms files to a subdirectory /cms (mimic original structure) on the new box. I have a .html redirect file in the Zeus root (Register365 idea) giving me access to the index.php file in the new Zeus /cms directory. So I flicked da DNS switch to point to the new box - DISASTER I can not get past the index page all site links giving ERROR 404s even when I login as admin user. Datatbase upload looks good re tables & records size wise etc. Could I have tripped an obvious gotcha? Clean URLs maybe knocking me out! Any help very welcome.

Regards
Bren

Hi There
Trying to restore a DB created with backup migrate.
When getting a list of destinations, with
drush bam-destinations
I run into this error.
Initialized Drupal site runireland.com at sites/runireland.com                                                             [notice]
Warning: The command callback function backup_migrate_drush_destinations has a deprecated name.  It must begin with        [notice]
drush_backup_migrate_.  Skipping hook functions.

Any ideas?

The resources tab of the developer tool that comes with Chrome/Safari shows that all background images within the CSS file get downloaded, regardless of whether or not they are shown.
So the CSS sprites file overwrites rule is used to display the image, but the image file is still downloaded in the background.
I guess it's just being smart - the images might get used as some point, eg with a javsascript event.

This isn't an issue with Firefox or Internet Explorer.
I ran a network sniffer to confirm this.
It's only a minor issue

In a follow-up to #849356: Does this really need to work on non-aggregated files?,
The module doesn't currently work when CSS aggregation is enabled.

I've had a look through the code, but I can't see the issue that's causing it.

On a broader sense, In terms of a plan of attack, I would suggest hooking into the CSS aggregation process, and manipulating the CSS aggregated file before it is saved at all.
This post
http://www.phpied.com/data-uris-mhtml-ie7-win7-vista-blues/
is the most comprehensive guide I could find in terms of how to manage all the different scenarios.

However, I don't like the browser sniffing employed in his example PHP class.
I think that the method used to satisfy IE on Vista would still work for all browsers [I still need to test this],
and that would be sufficient.
In this case, all background images are replaced by a single HTML file.
The original css is rewritten to point to this external css file.

Alternatively, we can do it 'properly' for normal browsers.
Rewrite the CSS file before saving the aggregated file.
And then add the 2 files in conditional stylesheets for IE7, IE6.
It does mean that they get the same information twice.

Its all a case of trade-off between satisfying different scenarios in any case.

Anyway, that's my 2c!

Alan

I ran the Coder module script through the module.
It picks up some syntax that doesn't comply with Drupal's coding standards.
Patch attached.

At the moment, this module works on non-aggregated CSS files.
I'm not sure that is really necessary.
It seem if you are concerned about reducing http requests [the aim of this module], then you'll have that enabled.

If that assumption is made, then coding could be a bit easier.
The work only need to happen when the aggregated css file is saved.

On the User interface, the setting to generate Data URIs could be disabled/hidden until the CSS aggregation box option was enabled.

Hi Dimitry
I'm continuing to test the module.
I have some thoughts on the interface.
If you agree with any of them, let me know, and I'll try to make some patches.

The overall principle I'm looking at is "Less is more".
Ideally a module should 'Just work'.
For example the jQuery Update modules simply needs to be enables in order to provide a new version of the jQuery Library.
No need for any configuration.
The pathauto module starts working straight away, but lets the user change the default settings.

So, with that in mind.

1. Settings page.
I don't know if there is a need for a separate settings page.
Ideally any configuration would be done directly on
admin/settings/performance
within the 'Bandwidth optimizations' section.

2. 32Kb per image limit
Is this setting really needed?
The reality is that IE7 and IE8 support is mandatory [from a practical point of view], so why would anyone uncheck that box?
The code could be written so as to make that available as an option if a future release [when usage of those browsers is lower], but not expose that setting to the user right now.
Is there was some extra work needed for IE6 only?
If so, then that could be an option, as many people [though not me just yet], choose not to support IE 6.

Regards
Alan