Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Was using this module without fail. Tonight after upgrading my site theme (or any other) will no longer load. When the module is turned off everything works again. Even touching to resynch items does not help
Comment | File | Size | Author |
---|---|---|---|
#25 | cdn-remove_farfuture_argument-2667494-25.patch | 461 bytes | Oleksiy |
#8 | Screenshot from 2016-02-26 12:51:56.png | 44.91 KB | Blau |
#8 | Screenshot from 2016-02-26 12:50:15.png | 245.51 KB | Blau |
Comments
Comment #2
Wim LeersOh no :( This is definitely critical.
Comment #3
Wim LeersComment #4
Wim LeersComment #5
venusrising CreditAttribution: venusrising commentedHi Wim-
I don't see any error logs. I did try this with core themes and it happened with all over them. I even tried turning off clearing cache and turning back on but no luck. It for some reason just won't grab the themes, content is there and I did notice a huge list of TAP to reload on images and pages.
Comment #6
Wim LeersP.S.: what is "TAP"?
Comment #7
Wim Leers#2667494: Follow-up for #2647830: version 2.7 broke Far Future expiration was closed as a duplicate of this.
Comment #8
Blau CreditAttribution: Blau as a volunteer commentedHello,
Sorry for the delay. I include 2 images of the home page before and after activation of CDN 2.7 module. And a third image showing that no error is detected in this module (neither in any other -not shown-).
CDN connected to Amazon. Bartik Theme and Drupal core versions: 7.42.
Blau
Comment #9
Wim LeersCan you post the contents of the
<head>
tag?Comment #10
Blau CreditAttribution: Blau as a volunteer commentedHead tags without (wo) and with (w) the CDN module activated have been attached.
Comment #11
Wim LeersThanks! I asked for that because it's clear from the screenshots no CSS is being loaded. But I can see that the URL actually looks correct:
So, can you say what the contents are of those CSS responses?
Comment #12
Blau CreditAttribution: Blau as a volunteer commentedNo file is found!
Comment #13
Wim LeersAnd everything worked fine with version 2.6 for you?
Comment #14
Blau CreditAttribution: Blau as a volunteer commentedYes, it did completely fine.
Comment #15
Wim LeersDid you happen to change your database name or credentials at the same time?
Comment #16
Blau CreditAttribution: Blau as a volunteer commentedNo. Although I updated Drupal core at the same time (of updating CDN). I do not know if this change in Drupal core could have some effect.
Comment #17
captainack CreditAttribution: captainack commentedThis may be a dupe. Can you try this patch?
Comment #18
captainack CreditAttribution: captainack commentedEDIT: Wrong thread :-!
Comment #19
Blau CreditAttribution: Blau as a volunteer commentedSorry, but I do not know much about code. Where should I include this patch?
Comment #20
captainack CreditAttribution: captainack commentedOkay.
Do you have a non-production staging or development site you can test it on?
Comment #21
Blau CreditAttribution: Blau as a volunteer commentedNot in the same conditions, but I will prepare it.
Comment #22
Blau CreditAttribution: Blau as a volunteer commentedDone. What should I do now to include the patch?
Comment #23
captainack CreditAttribution: captainack commentedGreat! You probably already know this, but make sure the cdn module isn't shared with your production site - like if the cdn module is in the /sites/all/modules that's shared with the production site, don't do it
After that... There are good instructions here on how to apply a patch: https://www.drupal.org/patch/apply
Comment #24
muldrow CreditAttribution: muldrow commentedI can confirm the exact same situation: CDN working great on 2.6, then breaking with 2.7.
Some further symptoms:
With far future set to on, everything breaks. It looks like all of the files return 403 errors when they are pulled.
With far future set to off, I'm unable to load new images into content because the style/thumbnails are generating into files that return 403 errors as well.
Cache clearing and monkeying with aggregation of files doesn't help at all. Reverting to 2.6 fixes everything back to normal.
I tried the patch above, but it didn't help.
Comment #25
OleksiyGot the same issue with files when updated CDN module to 2.7.
@captainack, thanks for the patch, it solves the issue for me.
Above the patch file is attached.
Comment #26
captainack CreditAttribution: captainack commentedThanks for confirming it Oleksiy!
muldrow ... Can you please confirm that you applied the patch correctly and confirm that this is indeed already covered? Were you able to pull the files by going to the farfuture path on your site directly?
Blau, did you have any luck with the patch?
Comment #27
Blau CreditAttribution: Blau as a volunteer commentedSorry! I tried to apply the patch, but I could not understand how to do that. If I am right I should access my server by SSH, isn't it? Is there another option, e.g. by Devel, or whatever different system?
Comment #28
venusrising CreditAttribution: venusrising commentedSorry for omitting the screenshot as I had corrected it with a rollback before I could grab it. Wim when I said to TAP there is text using Amazon that says to tap to re-load files ie if there has been a change etc. So even reloading the content did not help. Sorry for the delayed reply.
I don't have a test site available right now.
Comment #29
muldrow CreditAttribution: muldrow commentedI can confirm that the patch resolves these issues. Thanks!
Comment #30
fgmHad the same problem with Cloudfront when I upgraded to 7.43 and CDN 2.7. Applying the patch in #17 fixed the issue.
In my case I noticed it initially with the RSS feed icon, which got fetched from
http://osinet-cdn.osinet.eu/cdn/farfuture/eDyaLh9tnVQBqPfpUOgAnvGBDdmkvv...
... which translates to
cdn/farfuture/%(for token)/%(for tag)/(path)
but the hook_menu() entry expects
cdn/farfuture/%(for token)/%(for drupal_release)/%(for something else)/(path)
Removing the extra % addresses the issue, but maybe it breaks something else ?
Comment #31
Wim LeersDamn — sorry folks :(
This was broken in #2647830: farfuture, SEO, and "domain uses the same web server as this Drupal site" error message. @captainack also reported this over at #2647830-18: farfuture, SEO, and "domain uses the same web server as this Drupal site" error message. This slipped through the manual testing he did back then. Thanks for all the confirmations that this fixes the problem. RTBC'ing.
Comment #32
Wim LeersBetter title.
Comment #33
Wim LeersAnd this is why having comprehensive test coverage is so important :( We have
CDNOriginPullFarFutureTestCase
, but no integration test coverage, which would have detected this.It is exactly this brittleness why I'm looking forward to your feedback at #2708787: Port Far Future expiration to 8.x-3.x to determine whether it's worth porting the Far Future expiration support to the Drupal 8 version of the CDN module.
Crediting @captainack as the patch author, and crediting @muldrow and @fgm for their testing.
Comment #35
Wim Leers