What are the consequences of using latest JQuery?
I needed to use the latest JQuery release for my front page, so I was able to replace the core's version with the latest for only page-front.tpl.php. Later on during development, another developer decided to do the same replacement in page.tpl.php. I know this is a bad idea, but I how do I support that it's a bad idea? I see that some small issues with collapsible fieldsets on the admin and edit pages, but for the most part things work fine. What am I missing?? Thanks. Eric.
I am also facing same problem On 10/15/07, Eric Mckenna <eric.mckenna@gmail.com> wrote:
I needed to use the latest JQuery release for my front page, so I was able to replace the core's version with the latest for only page-front.tpl.php. Later on during development, another developer decided to do the same replacement in page.tpl.php. I know this is a bad idea, but I how do I support that it's a bad idea? I see that some small issues with collapsible fieldsets on the admin and edit pages, but for the most part things work fine. What am I missing??
Thanks. Eric. -- [ Drupal support list | http://lists.drupal.org/ ]
Did I post this to the wrong list? Kalyani Waychal wrote:
I am also facing same problem
On 10/15/07, *Eric Mckenna* <eric.mckenna@gmail.com <mailto:eric.mckenna@gmail.com>> wrote:
I needed to use the latest JQuery release for my front page, so I was able to replace the core's version with the latest for only page-front.tpl.php. Later on during development, another developer decided to do the same replacement in page.tpl.php. I know this is a bad idea, but I how do I support that it's a bad idea? I see that some small issues with collapsible fieldsets on the admin and edit pages, but for the most part things work fine. What am I missing??
Thanks. Eric. -- [ Drupal support list | http://lists.drupal.org/ ]
Eric Mckenna wrote:
Did I post this to the wrong list?
No.
I needed to use the latest JQuery release for my front page, so I was able to replace the core's version with the latest for only page-front.tpl.php. Later on during development, another developer decided to do the same replacement in page.tpl.php. I know this is a bad idea, but I how do I support that it's a bad idea? I see that some small issues with collapsible fieldsets on the admin and edit pages, but for the most part things work fine. What am I missing??
If it works fine, then how do you know it's a bad idea? :)
Fred Jones wrote:
Eric Mckenna wrote:
Did I post this to the wrong list?
No.
I needed to use the latest JQuery release for my front page, so I was able to replace the core's version with the latest for only page-front.tpl.php. Later on during development, another developer decided to do the same replacement in page.tpl.php. I know this is a bad idea, but I how do I support that it's a bad idea? I see that some small issues with collapsible fieldsets on the admin and edit pages, but for the most part things work fine. What am I missing??
If it works fine, then how do you know it's a bad idea? :)
Why i think its a bad idea: If it was that simple then why isn't there something on drupal.org about it? Why are there modules specifically built to integrate updated JQuery versions? And simplely replacing a core component of any piece of software is a bad idea unless you have an adequate testing harness, which I don't see for Drupal when it comes to the use of JQuery. Things work, but there are small issues, mostly on the admin pages, that I think could become a big issue at any moment. I don't want to get to that point. Remember, Drupal is packaged with JQuery 1.0.3! The most current version is 1.2.1. That's a big enough jump to expect some incompatibility. ;)
participants (3)
-
Eric Mckenna -
Fred Jones -
Kalyani Waychal