By primus on

I developed out a site on my local machine, everything works great, then moved the files and database to production and everything works EXCEPT when I go into any of the admin pages, if a section on the page is collapsed it cannot be expanded, therefore I cannot make any changes; getting the following errors:

Error: $("textarea.resizable:not(.textarea-processed)", context).each is not a function
Source File: http://kccg.org.previewdns.com/misc/textarea.js?4

Error: $("table.sticky-enabled thead:not(.tableHeader-processed)", context).each is not a function
Source File: http://kccg.org.previewdns.com/misc/tableheader.js?4

Error: $("#" + base + ".tabledrag-processed", context).size is not a function
Source File: http://kccg.org.previewdns.com/misc/tabledrag.js?4

All files are there, I've looked around for answers and cannot find any, I'm running Drupal 6.x.

PLEASE HELP, any ideas of the potential problem would appreciated.

Thanks

⋅ Categories: Drupal 6.x

Comments

Patricia_W’s picture

Patricia_W commented

I'm having the same problem and I am looking for a solution. I've noticed that sometimes I can update the body and sometimes not. I think I had identified it was related to a theme and when I switched to another theme I could update the body. But now I can't. I also cannot use FCKeditor but it works fine on my development site.

Patricia W

Patricia_W’s picture

Patricia_W commented

I suspect that we are both having the same problem. I too am using a previewdns.com subdomain (GoDaddy) so it is not a real production environment. I/we have not changed our name servers to point to the web host. I am also using GoDaddy for another website which is very similar and it works correctly. I have reloaded the database and client files and nothing changed so I am beginning to conclude that the only difference is the previewdns.com setup. I hope when I switch the name servers that it will work correctly.

Patricia W

Patricia_W’s picture

Patricia_W commented

I can confirm that the problem is resolved when the GoDaddy site migrates from the previewdns.com sub-domain into the main domain. I just did that and without making any other changes can now use FCKeditor (and the admin sections can be expanded.)

Patricia W

aiglesiasn’s picture

aiglesiasn commented

I had this problem too, i was about to cancel my godaddy account, but if it worked for you without the previewdns.com i think i'll keep working on this webserver...

Thank You for your post.

bmodesign’s picture

bmodesign commented

Thanks for posting about this. I ran into the same problem. The rotor module stopped working for me along with all of the other things... I would upload the test site on a live account somewhere else, say in a sub directory on your own hosting account, and test it there. Then move it to it's own account.

I did that (posted it on my account) then modified the site, and wanted to move it to the other live account. Of course the database was more than 2MB, so phpmyadmin didn't work (exporting & importing MYSQL). I had to backup the database using Godaddy's db manager, and then FTP it to my computer, then FTP it back to the hosting account I wanted the site on. I created the database on the new hosting account and 'restored' it with their db manager, using that backup from the other hosting account... that was fun.

Just posting for information sake.

tenten71’s picture

tenten71 commented

Thank you all for confirming my suspicions about GoDaddy's previewdns code making my life crazy. Before this, I couldn't figure out why some sites on GoDaddy would work and why some would not. Now that my suspicions have been seconded, I've come up with some temporary workarounds.

1) With the help of Firebug for Firefox, you can find the CSS code to turn off the collapsing function all together. In Drupal 5, in the MODULES > SYSTEM > SYSTEM.CSS file, comment out lines #302 to #335 (the Collapsing fieldsets section). All your collapsed fields will remain un-collapsed. Then un-comment them when you're ready to go live.

or

2) Disable "All Javascript" with Web Developer extension for Firefox. This unfortunately prevents TinyMCE from working but it's a temporary fix anyway.

Hope this helps alleviate some of the drupal tension.

www.TenTen71.com

And...

3) For a quick fix for the Drupal Install page effected by GoDaddy PreviewDNS code, use Firebug to temporarily open the bottom "advanced settings" panel. Find the css code that controls the collapsed state and change it to "display: block" in the right side of Firebug.

GDHosting’s picture

GDHosting commented

Sorry you guys are having trouble. We're looking into this and will follow up here soon.

agerson’s picture

agerson commented

I have this problem with Drupal 6.10 and GoDaddy preview DNS. Thanks for posting a work around.

gabemonster’s picture

gabemonster commented

Thank you for this info. It was driving me nuts!

I used the web developer extension for FireFox and disabled all JavaScript. I can at least work on publishing content until I push into production.

Thanks again.

roper.’s picture

roper. commented

An even better solution is to simply install the AdBlock Plus extension. Then you can just add a rule to block "http://support.previewdns.com/mt.js" as that's the real culprit here.

This way, you don't have to disable ALL javascript or edit the page via Firebug at all.

Hope this helps someone. :-)

ajlowndes’s picture

ajlowndes commented

you guys all seem to gotten further than I have with drupal and godaddy's previewdns. So I have a question which you may be able to help me with:
My site is up on the godaddy servers, and going to http://millarcreekcafe.com.previewdns.com presents me with drupals' "site off-line" message, with an error at the bottom saying
If you are the maintainer of this site, please check your database settings in the settings.php file and ensure that your hosting provider's database server is running. For more help, see the handbook, or contact your hosting provider.

The mysqli error was: Can't connect to MySQL server on 'millarcreekcafe.com.previewdns.com' (111).

my question is this: I have successfully created my database in mysql and imported my data to it via phpmyadmin, but I cannot find what to put into settings.php to make it find my database - I cannot put "millarcreekcafe.com" in this field, because that domain is still currently (and for the next 3-4 days probably) registered with my old hosting provider. I also tried pinging millarcreekcafe.com.previewdns.com and putting that IP in there, but got the same error.

any ideas?

thanks

ajlowndes’s picture

ajlowndes commented

hey so i have done some more research and it turns out my post above is not quite on topic for this thread. i was at a different stage in my thinking then. anyway, i have fixed that problem by just installing with godaddy's preconfigured drupal installation.
the previewdns issue you were all talking about however, remains. turns out from other sources that previewdns.com domains do not work with jquery.
solution to view your site if it's on previewdns is here: https://forum.hostingmetropolis.com/user/discussion.aspx?id=163532
but it will only work on that computer - if you want your previewdns site to work on multiple computers (say lots of developers working on it) then i dunno. that's something that godaddy has to address i guess.

islamegy’s picture

islamegy commented

This error occurred because previewdns.com inject some javascript code at the end of your files to display the alert in each page.
They use a library called moo (http://mootools.net) this library use assign itself to the "$" variable, so if you use jquery this will cause a conflict as any call to jquery functions using "$" will now try to call moo library.

I don't use drupal and my application is asp.net but i believe the solution is valid for anyway
the solution is easy:
1- After include jquery, assign jquery to different variable
<script type="text/javascript" language="javascript" src="js/jquery.js"></script>
<script type="text/JavaScript">
<!--
var $j = jQuery.noConflict();
-->
</script>

2- change all "$" to "$j" in all your files

it should work now, more details for jquery conflict with other libraries is here http://docs.jquery.com/Using_jQuery_with_Other_Libraries

ejohnson’s picture

ejohnson commented

^ That solution seems sort of ridiculous when so many modules nowadays use the JQuery library and has dollar signs. Especially when you update modules every month for security/feature updates! Why wouldn't Drupal out of the box implement the jQuery.noconflict(), so that contributed modules follow suite and then you could also use the mootools library?

Ropers solution works too, but is also flawed when so many clients still use Internet Explorer. For the most part, training clients on Drupal is enough for them to wrap there brains around, let alone trying to instruct them about this hack.

Is there any global solution for this Godaddy problem? Do I need to get a dedicate IP to get around this until the site goes live?

Thanks.

roper.’s picture

roper. commented

I posted a reply earlier in the thread (http://drupal.org/node/275426#comment-2487320) but it could've easily been overlooked, so please check it out if you're still having problems.

:-)