Hi, I have followed the instructions in the documentation and am seeing some strange results. I am using Drupal 6.19 and the 6.x-2.x-dev version of the cdn module. I have applied the drupal6.patch and the status is reporting that the patch is applied correctly.

All url's are printing as :

http://domain.com/cdn.domain.com/cdn.domain.com/sites/domain.com/files/i...

I walked through the patch manually as well to make sure the changes had been properly implemented. I have not seen this kind of behavior before...Can someone give me information to track this or how I can provide more information to explain why this would be happening???

Comments

stevenator’s picture

stevenator commented

I forgot to mention I am in the basic/origin pull mode and the cdn url is set to: cdn.domain.com. The same pattern applies to all allowed extensions: .ico .gif .jpg .jpeg .png .svg .otf .ttf .swf

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented
Assigned: Unassigned » wim leers
Category: bug » support
Status: Active » Postponed (maintainer needs more info)

Please go to the admin/reports/status and ensure that it says there that the core patch is correctly applied.

stevenator’s picture

stevenator commented
Status: Postponed (maintainer needs more info) » Closed (works as designed)

Hi Wim,

So yes, the status report said that the core patch was applied correctly. After following my file_create_url's for about 3 hours, I found the root of my problem to be with the Pathologic module. Given better understanding of the circumstances I picked better search terms in Google and found these:

Skip root-relative and protocol-relative URLs and support the Pathologic module, http://drupal.org/node/477332
Problems with shipped files and Drupal 6 file_create_url() behavior http://drupal.org/node/971712
Non-filter URL rewriting http://drupal.org/node/820910

which was right on the money. Turned out to be both a cache problem (can't clear it enough during development sometimes) and the Image/Img_assist/Pathologic modules. After some monkey wrenching I found my problem and it was not with the CDN module

Lastly, thank you so much for this module. I don't know if you were aware but there was a presentation in September in LA at the LA Drupal meetup and a large part centered around the CDN module. So a personal thank you for both you thesis and this module. I have chosen to be a first adopter in the new Amazon custom origins for Cloudfront and have posted on that thread in the issues cue. I thought that may have been part of the problem but CDN runs perfectly with it (as it is a little outside the scope of the module once you set up the Cloudfront instance).

thank you and thank you.
Steve

wim leers’s picture

wim leers
Location Ghent 🇧🇪🇪🇺
commented

I had no idea the CDN module was a large part of a presentation at the LA Drupal meetup. Nice to hear! Are the slides online somewhere? :)

stevenator’s picture

stevenator commented

Hey Wim, sorry about never replying to this. I do not believe that the slides were ever posted as it was an open mic kind of presentation by @christefano, one of the LA Drupal organizers.I was back on this page to jog my memory on this and saw your reply but it never came down in my subscriptions.

Hope you are well and doing fine in the new JOB!