Currently this module's 7.x-2.x branch NEEDS TESTING. We ask that people CREATE NEW ISSUES about any bugs found, feature requests or desires to discuss about remaining tasks. No one should post in this issue. This issue is strictly for keeping track of the overall progress required to port this module to D7 and will be updated when tasks are added, completed or removed. This issue will close when a relatively stable 7.x-2.0-rc1 is released.
Completed tasks
- Made installable and loadable.
- Refactor administrative user interface.
- Fixed Admin Menu integration.
- Separated advagg.module into several smaller and more manageable files.
- Replace module code with core functionality where possible (ie: new D7 APIs, functions, etc).
- Refactor the CSS processing functions as the data arrays have drastically changed in D7.
- Refactor the JS processing functions as the data arrays have drastically changed in D7.
- Refactor status report page for correct requirement checks.
- Refactor drush integration.
- Fix any cron issues.
- Fix any async issues.
- Refactor advagg_js_cdn (will do nothing if jquery_update is installed).
- Refactor advagg_bundler
- CSS/JS Compression Submodule: Testing, Caching, & Inline Compression #1943522: Testing, Caching, & Inline Compression of CSS/JS
- Move JS to footer module #1743910: Move JS to footer
- Per page (blocks style) Inline CSS/JS and/or different bundle settings #1743910: Move JS to footer
- Unified aggregation directory submodule #1082928: Unified Aggregation Directory
Remaining tasks
- Ensure compatibility with the following modules:
jQuery Update,CDN,LABjs,CSS Embedded Images - Update README.txt #1977048: update readme.txt
- Create an API file #1977044: create an advagg.api.php file
- Document all files and functions.
#1946218: test with other modules & themes
Wish List (ie: not critical for release)
- Create CHANGELOG.txt to keep track of any API or function changes.
UI & UX - Additions/Changes/Removals
- CHANGED:
- Admin UI configuration is now located at:
admin/config/development/performance/advagg.
Original report by dropbydrop
when do you expect a drupal 7 version to come out?
thanks
| Comment | File | Size | Author |
|---|---|---|---|
| #96 | advagg-fix-display-js-compression-admin-tab-1171546-96.patch | 628 bytes | piouPiouM |
| #71 | advagg-1171546-71-fix-public-download-get-into-d7-hooks.patch | 21.68 KB | mikeytown2 |
Comments
Comment #1
mikeytown2 commentedOnce advagg hits a full 1.0 release; I will start to work on the 7.x-2.x series.
Comment #2
dropbydrop commentedExpected Time of Arrival?
Comment #3
mikeytown2 commentedHard to say; if I didn't have work + my other modules fighting for my time it would be done sooner.
List of modules that I'm directly responsible for that need more love:
http://drupal.org/project/views_javascript_random
http://drupal.org/project/views404
http://drupal.org/project/location_display
http://drupal.org/project/imageinfo_cache
http://drupal.org/project/imagefield_zip
http://drupal.org/project/dbtuner
http://drupal.org/project/expire
http://drupal.org/project/boost
http://drupal.org/project/css_gzip isn't in that list because this project will replace it.
In terms of my todo list:
#1060358: CDN and SEO in harmony with my files proxy module.
I need to fix some issues for boost 7.x
Then I'll come back to advagg 7.x most likely.
Comment #4
dropbydrop commentedI wish I knew how to develop to contribute!
Comment #5
mikeytown2 commentedGoing to mark this as postponed until I get some things done.
Comment #6
pounardSubscribing to this issue.
As we quickly discussed on #1014086: Stampedes and cold cache performance issues with css/js aggregation, I'd like to merge some effort. I wouldn't like to intervene on heavy CSS/JS aggregation stuff, you do it well. I'd like to see some of this code (dynamic and on-demand file generation based on the Stream Wrapper core API) being generic, modeled depending on a real practical use case (AdvAgg module seems a good one). I could also make Core Library original module being lightweight and usable in duo with AdvAgg.
Open to suggestions, discussions, and ready to help. I could even try provide a PoC patch for your module's base (not all features) working over my code base ported to D7 if I find some time, that's not a promise though.
Comment #7
mikeytown2 commented@pounard
Still working through creating an api for this issue #1174908: Option to output JS/CSS as a files array. Once advagg is 1.0 final I'll be more vocal about how we can work together.
Comment #8
pounardOk, I'll wait for it! I saw that you need a lot of work if you want to get this working into D7, you are using huge array data structures that doesn't always fit with
hook_(css|js)_alter()D7 hooks, and for an easy porting you'll need this I think.Comment #9
mikeytown2 commentedComment #10
anavarreSubscribe
Comment #11
damienmckenna#want. I might get the ball rolling with a quick through Coder, see what happens :)
Comment #12
damienmckennaI ran the latest AdvAgg d6 code through the latest version of Coder and ended up with a large TODO list to work through. I'll see if I can get time to do it in the next day or two.
Comment #13
mikeytown2 commentedA straight conversion over can't be done easily. Certain advagg hooks are very similar to D7 core hooks; thus we can use core versions for these hooks.
drupal_get_css
hook_css_alter
drupal_get_js
hook_js_alter
Other things need to be considered as well. I plan on calling the 7.x version of advagg 2.x because it will be quite different from 1.x; but it will offer the same functionality & the sub modules shouldn't have to be changed that much.
Comment #14
dboulet commentedSubscribe, sounds like an interesting module.
Comment #15
pounard@mickeytown2 would you consider using my work in 7.x-2.x branch of Core Library module?
Comment #16
mikeytown2 commented@pounard
Once I start to look at creating a D7 branch, I'll be looking at both projects; Core Library & Aggregate cache. Thats the "magic" of the GPL #1066672: Duplicate module with 2 others, merge would be a good thing #1066818: Unneccessary Branching? #1063316-1: hook_init() necessity. As I've stated above I need to work on the 7.x version of boost before taking on this issue.
Comment #17
pounardYes, thanks for answering. My answer is still I'm ready, not for merging necessarily, but at least to adapt as much as it could be useful. Module duplication is not always bad, it depends on the needs, mine's goal is still to remain simple, but its core (file generation) is quite generic and can be exported as a module on its own, and easily shared thus avoiding code duplication. It's up to you!
Comment #18
Fidelix commentedSubscribing...
Comment #19
bryancasler commentedsubscribe
Comment #20
mrfelton commentedsubs
Comment #21
leguy commentedsubscribing
Comment #22
bryancasler commentedFor comparison, there seems to be similar work happening for wordpress.
http://wordpress.org/extend/plugins/w3-total-cache/
Comment #23
c4rl commentedSubscribble
Comment #24
paulgemini commentedsubbing
Comment #25
kiphaas7 commentedsub. And willing to contribute patches :).
Comment #26
mgiffordI'm very interested in the w3 total cache implementation.
Comment #27
mstrelan commentedsubscribe
Comment #28
samgreco commentedsubscribe
Comment #29
MacRonin commentedsubscribing
Comment #30
rumblewand commented+1
Comment #31
dropbydrop commented+1
Comment #32
basicmagic.net commentedsubscribe
Comment #33
obrienmd commentedsubscribe
Comment #34
pillarsdotnet commentedComment #35
Coupon Code Swap commented+1
Comment #36
migala commentedfollow
Comment #37
kiphaas7 commented#36, you don't need to post comments to follow topics anymore. You can simply hit the 'follow' button next to the topic start. See also this post:
http://drupal.org/node/1306444
Comment #38
andypostSuppose project page should be updated to point Aggregate cache for D7
Comment #39
wim leersSubscribing.
Comment #40
jamesoakley@Wim Leers:
you don't need to post comments to follow topics anymore. You can simply hit the 'follow' button next to the topic start. See also this post:
http://drupal.org/node/1306444
Comment #41
wim leers@JamesOakley: LOL! I apologize! I knew about that, but it's been a habit for almost 5 years now. Thanks, and my apologies! :)
Comment #42
mikeytown2 commentedFor things that are feature requests, I actually like seeing a "Subscribing" message; lets me know who's wanting it. And in this case AdvAgg is now tied to CDN so thats more more fire under my rear to get this going.
Once we get the D7 site for work live, AdvAgg is the first module to be ported. ETA for a beta is late February.
Comment #43
wim leersGreat :) Expect a new, very solid release of the CDN module for both Drupal 6 and 7. Feature parity. Advanced Help support. Various of your patches. Etc. :) I'm actually already referring to the AdvAgg module in the Drupal 7 module's documentation in the same way as the Drupal 6 module. I was already assuming it'd get ported :)
Comment #44
Anonymous (not verified) commentedFeature request for drupal.org: the number of followers unther/above the follow button....?
Comment #45
pounardThe name of the followers :)
Comment #46
bryancasler commentedRE-SUBSCRIBING
Comment #47
Fidelix commentedAh... well... this would be great for some big projects I have on my plans.
Comment #48
melon commentedThis is really good news, I can't wait to help with testing the D7 port. (re-subscribing)
Comment #49
thirdboxcar commentedsubscribe
Comment #50
heyyo commentedSubscribing with pleasure :-)
Comment #51
broncomania commentedsubscribe
Comment #52
omega8cc commentedYou don't need to add comment just to subscribe only - instead use the big Follow button at the top right ;)
Comment #53
kiphaas7 commentedomega: http://drupal.org/node/1171546#comment-5500878
Comment #54
omega8cc commented@Kiphaas7: Ah! I missed that comment, thanks.
So +1 from me :)
Comment #55
tebb commented@MikeyTown2: Subscribing ... as requested: http://drupal.org/node/1171546#comment-5500878
Comment #56
AdrianB commentedThis is off topic, but since it's been brought up I thought I should provide the correct issues:
cmseasy: #1304550: Display count of issue followers when viewing an issue
pounard: #1304558: Provide a page showing all the users following a given issue
Comment #57
mcferren commentedsubs
Comment #58
JeremyFrench commentedAlso subscribing.
Comment #59
dergachev commented+1
Comment #60
gynekolog commentedStop subscribing, start following -> http://drupal.org/node/1306444
Comment #61
mikeytown2 commentedThis will be worked on at the Drupalcon code sprint on Tuesday and Friday. Come by to help out!
http://denver2012.drupal.org/sprints
Comment #62
sprice commentedThe need to write the subscribe message on this particular issue is no longer needed as the number of followers is displayed just under the "Follow" button now. New feature on d.o implemented this week! So, the new subscribers need not post the requested message anymore.
Comment #63
melon commented@gynekolog @sprice please take the time to read this thread before commenting. Especially #42 is for your attention, folks!
Comment #64
gynekolog commented@melon mikeytown2 now knows how many people want this module. Number of followers is displayed under "follow" button now. Read more carefully!
Comment #65
sprice commented@gynekolog — Exactly.
@melon — My comment was in reply to #42 in regards to the new feature implemented on d.o this week that takes care of the number. If @mikeytown2 wants to see the names of the people subscribing, then new people should still subscribe. If it's just the numbers that matter, then look under the "follow" button, and, as of this writing, you can see that 96 people are following this thread (by far more than most other threads that I've seen!).
Comment #66
melon commented@gynekolog @sprice Sorry I didn't notice that the number of subscribers is now available.
Anyhow, I'm looking forward to the outcome of the sprint at Drupalcon!
Comment #67
mikeytown2 commentedInitial deep dive into the APIs.
Unfortunately drupal_get_css() isn't nice. drupal_pre_render_styles() looks like the thing I wish to modify, but I can't do it. I might be able to get in by changing system_element_info() via hook_element_info_alter(). This is what pounard's Core Library does in resource_element_info_alter(), switching drupal so it uses resource_aggregation_aggregate_callback() instead of drupal_aggregate_css(). Catch's argcache also uses hook_element_info_alter and it seems to be a simpler way to do it as it doesn't implement its own stream wrapper.
Moving forward I will try my best to use hook_element_info_alter() to accomplish what I need... but for JS I will still need hook_theme_registry_alter. The other nice thing is for some of the advagg sub modules is core's hook_js_alter() and hook_css_alter().
I think I have a good way to hijack css & js processing. I should have a start on this hopefully by the end of friday; I now know what needs to happen to make this fly in D7. No code from yesterdays sprint, just investigating how some D7 modules do what I want to do.
Comment #68
bryancasler commentedso exciting!
Comment #69
doublejosh commentedSome progress. Applied the coder module upgrade changes and created a branch to get this process going.
3cc1801afd490c6e9fa4a2a8cb36e204cd639a85
This is untested and just a working start. Do not use without intent to help debug.
Comment #70
doublejosh commentedOne of the first issues to deal with will be to remove the public file system logic, found discoverable near FILE_DOWNLOADS_PUBLIC.
Comment #71
mikeytown2 commentedThis patch has been committed. Fixes public downloads and advagg now uses the correct hooks for D7. For now I have copies of core's functionality. Code is still not production ready.
Comment #72
klonosHow about a 7.x-dev please?
Comment #73
mikeytown2 commented@klonos
For now git is the way to test & fix the 7.x branch. http://drupal.org/project/advagg/git-instructions. Once it actually works I'll make a 7.x dev. Core had some big changes in how CSS & JS files work; this is a big project.
Comment #74
klonosFair enough. Just make sure you update this issue when a 7.x-dev is available please.
Comment #75
dave_______1 commentedSubscribing
Comment #76
likewhoa commented@dave_______1 stop subscribing and start following FFS. see top of every issue queue.
Comment #77
kiphaas7 commentedlikewhoa, you should have read the topic.
http://drupal.org/node/1171546#comment-5500878
Comment #78
gynekolog commentedKiphaas7 - http://drupal.org/node/1171546#comment-5747832
Comment #79
likewhoa commented@Kiphaas7 ^
Comment #80
amfriedman commented+1
Comment #81
escapeit commentedsubscribe
Comment #82
hariskar commentedsubscribe
Comment #83
Rick G commented+1
Comment #84
vinmassaro commentedSubscribing, would like to see this for D7 or know what alternatives are out there to fix the broken aggregated CSS/JS issue.
Comment #85
markhalliwellCan we please get the 7.x branch on d.o rolling instead of commenting on subscribes? Also, even on the git repo, there hasn't been work done on the 7.x branch in months.
What can I do to help?
I will gladly spend time on this as it is greatly needed. There will never be a stable release until at least a dev is rolled out. Not to mention, creating a d.o dev branch will allow the needed version tag for the issue queue. This way we can start managing what needs to get done.
I'll open another issue to become a co-maintainer.
Comment #86
markhalliwellComment #87
markhalliwellATTENTION: The 7.x-1.x-dev snapshot release and been created.
Please file any bugs with the 7.x branch as a NEW issue so they can be properly tracked. DO NOT post bugs in this issue and please no more subscribes. If you would like to be notified, click the big green "Follow" button at the top. This issue will be marked as fixed once there is a 7.x-1.0-rc1 release.
NOTE: Currently the 7.x-1.x-dev snapshot is no where near ready for production use and is only for those who wish to test and debug the 7.x branch.
http://drupalcode.org/project/advagg.git/commit/fb93315
I went ahead and made AdvAgg at least installable and "loadable". Please keep in mind that there are a TON of API changes from D6 to D7 and it will take time for everything to be fixed.
Comment #88
hariskar commentedI get errors and can't uninstall it.
Comment #89
hariskar commentedThis is the error message: Warning: rtrim() expects parameter 1 to be string, array given in file_prepare_directory() (line 437 of /home/www/hariskar/mikroviologos.gr/www/includes/file.inc).
If I disable it in the modules list and click save an empty page opens. If I refresh it is still enabled. So how can I uninstall it?
Thank you!
Comment #90
jamesoakleyDo you have access to drush on that server? If so, you could disable the module and then flush all the caches from within drush.
Comment #91
hariskar commentedThank you, but I don't have access to the server. Any other solution?
Comment #92
hariskar commentedHere is another error: Warning: strpos() expects parameter 1 to be string, array given in file_uri_scheme() (line 200 of /home/www/hariskar/mikroviologos.gr/www/includes/file.inc).
Comment #93
jamesoakleyDoes this help you?
http://drupal.org/node/157632
Note the bit about clearing the bootstrap cache - actually, IIWY, I'd empty all the table that start with "cache".
Disclaimer: If I were you, I'd take a backup of the database before doing any of that!
Comment #94
markhalliwell@hariskar: I agree with James, BACKUP first! If you don't have access to the server, it sounds like it's a production site. I would STRONGLY recommend against installing the dev version as this probably WILL break your site.
@EVERYONE: For those who are not familiar with module development or install a fresh local D7 site to test this module, this is NOT for you.
Comment #95
hariskar commentedI restored my site from yesterdays backup. Thank you!
Comment #96
piouPiouM commentedThe following patch fixes the display of the tab "JS Compression". Indeed, only the string "Array" is currently displayed.See #1669952: [META] AdvAgg D7 - JS Compression not working.
Comment #97
piouPiouM commentedSorry for the precedent bug report and status updates. I will immediately create a new ticket.
See #1669952: [META] AdvAgg D7 - JS Compression not working.
Comment #98
mgiffordDid you create the new ticket?
What is the status of the patch?
Some similar errors reported in the forums as here:
http://drupal.org/node/1445568
Errors I'm getting are:
Comment #99
jamesoakleyIs it #1669952: [META] AdvAgg D7 - JS Compression not working?
Comment #100
js commentedHi,
Is this 7.1-dev version useable for a live site yet?
Comment #101
playfulwolf commentedon BOA Nginx it is not.
Comment #102
omega8cc commentedI don't think it works for anyone on any web server. Just note that the last 7.x commit says just "Made module at least installable and loadable." It is not expected to work, yet.
Also, I don't think it is a task, but feature requests, and not critical, since it is *not* expected to work at this stage.
PLEASE read #87 above and DON'T post issues in *this* thread.
Comment #102.0
js commentedjust a note pointing to comment #87
Comment #103
markhalliwellhttp://drupalcode.org/project/advagg.git/commit/7c53d59
Also updated issue summary, please read and add/change/remove anything that still needs to be done. Please feel free to create meta issues as well.
Comment #103.0
markhalliwellUpdated issue summary.
Comment #103.1
markhalliwellUpdated issue summary.
Comment #103.2
markhalliwellUpdated issue summary.
Comment #103.3
markhalliwellUpdated issue summary.
Comment #103.4
markhalliwellUpdated issue summary.
Comment #103.5
markhalliwellUpdated issue summary.
Comment #103.6
markhalliwellUpdated issue summary.
Comment #104
markhalliwellPer #13:
I created the 7.x-2.x branch and will be working on that from now on. 7.x-1.x will never have a stable release or a direct port from 6.x, as Mikey said it's quite different [code wise].
Comment #104.0
markhalliwellUpdated issue summary.
Comment #104.1
markhalliwellUpdated issue summary.
Comment #104.2
markhalliwellUpdated issue summary.
Comment #104.3
markhalliwellUpdated issue summary.
Comment #104.4
markhalliwellUpdated issue summary.
Comment #104.5
markhalliwellUpdated issue summary.
Comment #104.6
markhalliwellUpdated issue summary.
Comment #104.7
markhalliwellUpdated issue summary.
Comment #104.8
markhalliwellUpdated issue summary.
Comment #104.9
markhalliwellUpdated issue summary.
Comment #104.10
markhalliwellUpdated issue summary.
Comment #104.11
markhalliwellUpdated issue summary.
Comment #104.12
markhalliwellUpdated issue summary.
Comment #104.13
markhalliwellUpdated issue summary.
Comment #104.14
markhalliwellUpdated issue summary.
Comment #104.15
mikeytown2 commentedUpdated issue summary.
Comment #105
mikeytown2 commented7.x-2.x dev has been pushed from my test sandbox #1917802: Drupal 7 Sandbox. As of right now the dev link is from January; wait for the one from March.
Notes:
- Upgrade path will not be provided but patches welcome (nuke all old data is the correct upgrade path). Uninstall of old module (1.x & 2.x) before using the latest version is highly recommended.
- Remove old advagg directory before installing the latest 7.x-2.x code.
- Latest code works 100% on my local test box, but there will be bugs. You have been warned.
Big Changes:
- CSS/JS CDN module uses core's hooks and as a result does not require advagg.
- CSS/JS CDN module is disabled if jquery_update is installed as it has the same functionality.
- 3 DB tables instead of 2.
- 3 hashes instead of 1 for filenames (readme.txt explains this change).
- A lot of advagg hooks can be placed in *.advagg.inc files instead of the *.module.
- Can use the httprl module but it is not required.
- Bundler logic has changed slightly; it should pick slightly better merges now.
Things to do:
- Add back in Admin Menu integration #1943218: Admin Menu Integration
CSS CDN module:
- Discovered a core bug #1937860: seven_css_alter does not set the type when developing it. Getting this fixed would be nice.
CSS/JS Compression Submodule:
- Will need httprl in order to do compression testing (not written).
- Cache compressed js. Provide a way to flush that cache.
- Inline CSS/JS compression.
Submodules to create:
- js footer (move js from header to footer via admin page) #1743910: Move JS to footer
- landing page inliner/optimizer (inline all CSS and JS AND/OR create a big bundle for faster loading of selected pages) #1311574: Disable bundler and swap to inline styles (for single use type pages)
- Unified Aggregation Directory #1082928: Unified Aggregation Directory
Will need to test:
http://drupal.org/project/jquery_update
http://drupal.org/project/css_emimage
http://drupal.org/project/cdn
http://drupal.org/project/labjs
http://drupal.org/project/headjs
Comment #105.0
mikeytown2 commentedUpdated issue summary.
Comment #105.1
mikeytown2 commentedUpdated issue summary.
Comment #105.2
mikeytown2 commentedUpdated issue summary.
Comment #105.3
mikeytown2 commentedUpdated issue summary.
Comment #105.4
mikeytown2 commentedUpdated issue summary.
Comment #105.5
mikeytown2 commentedUpdated issue summary.
Comment #106
klonosThanx for the update Mike!
Comment #107
wim leersAre these "CSS/JS CDN modules" really necessary? It looks (I looked at their code) like they don't really belong to be part of the advagg module. But then again, they do leverage advagg-provided hooks, which I guess is why you need them to live in the advagg module?
Let's make sure that advagg+cdn work well together again :)
The D7 CDN module comes with quite a bit of test coverage.
I think that in the D6 advagg era, one had to use advagg to have CDN'd background images in aggregated CSS files etc? That's no longer the case in D7: the D7 CDN module overrides Drupal core's CSS aggregation, just to wrap each external file in a
file_create_url()call (so that the CDN module'shook_file_url_alter()implementation gets called). I plan on getting that in a D7 point release, because it would move quite a bit of code out of the CDN module.Comment #108
wim leersAlso please make sure that you check the CDN module's new features, so that you don't provide the same functionality again :)
Comment #109
mikeytown2 commentedAdvagg cdn sub modules load jQuery & jQuery UI from the Google cdn. They do nothing if jQuery update module is installed. Will be testing with cdn module soon.
Comment #110
vinmassaro commentedThe 'broken CSS after cache flush when CSS aggregation is enabled' issue that was present in Drupal 6 has been fixed in Drupal 7 core, correct? Just want to double check since we were interested in using Advagg solely for this reason.
I see there is now a drupal_delete_file_if_stale() callback used in drupal_clear_css_cache() that leaves aggregated CSS around for 30 days in case Drupal page cache or external caches are still serving pages with references to old aggregated CSS. This was a real pain in D6.
Comment #111
mikeytown2 commented@vinmassaro
I'm pretty sure D7 core has that fixed to a better extent, but it is not 100%. drupal_delete_file_if_stale() will delete the file if it hasn't been modified in the last 30 days. The issue is, what if that aggregate has not been modified in the last 30 days but is still being used. drupal_build_css_cache() does a simple file_exists check which does not update the mtime. It is still possible to get a 404 with css files using D7 core, it's just a lot harder to now.
AdvAgg makes 404s even harder to encounter because it uses an imagecache naming convention, meaning that based off the name it knows how to create that file. The other thing is AdvAgg uses a cache & database to keeps track of atime ( updated once every 12 hours ), and if the file hasn't been accessed in the last 30 days it will remove that file from the file system (vs core using the last modified time). Even with that file deleted, it can still be generated though thanks to the imagecache naming convention. As it stands the only way to get a 404 using AdvAgg is if an aggregate has not been used in the last 6 weeks as that is how long it takes to clean up old entries in the database (advagg_cron() calls advagg_remove_old_unused_aggregates()); so you might get a 404 for css/js when accessing the page via google cache or archive.org (totally acceptable in my book).
Comment #112
mikeytown2 commented@Wim Leers
#1942230: CDN module AdvAgg 7.x-2.x Integration
Comment #113
mikeytown2 commentedThe first alpha version of AdvAgg 7.x has been released.
Summary:
- Readme.txt is not updated.
- Everything is working except for CDN's farfuture option.
- If using jQuery Update the advagg_css_cdn and advagg_js_cdn sub modules should be disabled.
- Uses httprl for aggregate building if module is installed.
- New sub module called advagg_mod; allows for tweaks to the css/js like put all JS in the footer.
- Need css_emimage 7.x-1.3 or higher; Older versions of module will not work.
Comment #114
tjharman commentedHi,
I have installed and am running this on two sites (based from a single multisite install) on Drupal 7.22.
All I can say it, it works! It works well, I haven't noticed any problems or issues since installing it. I'm using it in conjunction with CSS Embed images as well, it's functioning correctly too.
I'm also using the jsmin.so module compiled into PHP.
So I just wanted to provide some feedback that it's working well, and to say thank you!
Comment #114.0
tjharman commentedUpdated issue summary.
Comment #115
vinaykprao1987 commentedCSS aggregation not happening through advagg when CDN module is enabled. aggregated CSS being served through sites/default/files/public//cdn/css/http/[aggregated_name]css
Comment #116
mikeytown2 commented@vinaykprao1987
The patch #1942230-6: CDN module AdvAgg 7.x-2.x Integration for the CDN module states that farfuture is not working. If you go to the status report
admin/reports/statusit should also state that farfuture doesn't work and recommends that you disable it. Also please open up new issues or comment on the existing relevant issue instead of posting in here :)Comment #117
vinaykprao1987 commentedSorry about that did not check the Status Report. Had almost given up on the module. The patch worked. Thanks for all the help.
PS: I was not trying with far future option of CDN, without the patch CSS aggregated URL's was that of CDN rather than advagg.
Comment #118
philsward commentedAnybody notice a performance hit from advagg_bundler_analysis? I even disabled the bundler to see if I could get rid of the performance hit but in "most" cases, it still runs and takes up almost a half second worth of queries... :-/
Here's my Devel output:
I don't know enough about how the module works to know what's going on, just doing some initial investigation into the matter. If it's indeed a bug, I'll get a new issue going.
Thoughts?
Comment #119
mikeytown2 commented@philsward
Go ahead and open up a new issue. I can't repo what you're describing butsomething similar was an issue with the 6.x module #1283522: Slow query / number of bundles in advagg_bundles. Noted that the 7.x code has had some optimizations done to it #1927578-9: Get end to end prototype working. I've opened up a new issue #2006468: Slow Query in advagg_bundler_analysis. Run query in the background (via httprl) if at all possible.Comment #120
philsward commentedThanks @mikeytown2
I'll follow the other issue and help out with testing where I can :-)
Comment #121
mikeytown2 commentedrc1 of AdvAgg is now out. Marking this issue as fixed.
Comment #122
klonosThanx Mike! ;)
Comment #123.0
(not verified) commentedUpdate issue