I use IMCE 6.x-1.3 (An image/file uploader and browser), this module disables IMCE with an error message that says:

$.translate is not a function
[Break on this error] $.translate(function() { // After translation engine is ready.

please help! I need both modules and I prefer this one over the Translatable Comments module.

CommentFileSizeAuthor
#7 tr.jpg8.61 KBvako
#2 translatableregions.hide_translate_button.patch727 bytesrfay

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Title: Module destroys the IMCE functionality » IMCE conflict with Translatable Regions
Priority: Critical » Normal

To help you, I'll need you to upgrade to the current recommended IMCE (6.x-2.0-beta3).

Also, please let me know what other modules you're using that might be related (wysiwyg? imce wysiwyg api bridge?)

Thanks,
-Randy

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Needs review
StatusFileSize
new translatableregions.hide_translate_button.patch727 bytes

I was able to use translatableregions successfully with IMCE 6.x-2.0-beta3, IMCE Wysiwyg API bridge 1.1, and Wysiwyg 6.x-2.1.

I did find one warning I hadn't seen before - patch attached.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Needs review » Postponed (maintainer needs more info)

Committed to HEAD: http://drupal.org/cvs?commit=382298. The problem does not exist in the Drupal 7 version.

However, the error mentioned here does not cause IMCE to fail, and is invisible if admin/settings/error-reporting is set to "write to the log".

I'm going to set this issue to postponed, waiting for your input. Please report back about your experience with the updated modules.

vako’s picture

vako commented
Status: Postponed (maintainer needs more info) » Needs review

Thanks for the quick response.
I updated the modules as requested, applied the patch and ran update.php, but still getting the same error when I open the IMCE browser and the top toolbar is not visible (where it shows the upload, resize options)
The error-reporting is set to "write to the log", the error I am seeing is in the Firebug.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Needs review » Active

I'm able to upload, resize, and place images using IMCE. I'm testing in an Ubuntu environment, Apache, PHP 5.3.

Again, please provide more details about your environment. It's possible that there is some other module involved in this.

Here's some things I recommend as far as a debugging process.

* Try disabling modules to see when the problem goes away. Keep good notes.
* Try a fresh Drupal install with just the modules you're trying to make work together (IMCE, translatableregions, whatever else you must have). See if it works there.

http://randyfay.com/debugging has some general recommendations on debugging strategies.

vako’s picture

vako commented

OK thanks. I will try it later, on a 'virgin' installation, meanwhile I had to disable the module so the IMCE will work. Will keep you updated soon.

vako’s picture

vako commented
StatusFileSize
new tr.jpg8.61 KB

Hi Randy, there is something seriously wrong with this module.
Here's what I did:
- created a new site with a new installation of Drupal 6.17
- copied only the latest versions of the required modules you suggested above.
- created a new page -> this module disabled the editing section of the page (please see the attached image)

You can test it yourself by logging to the site as follows:

domain: www.nikolian.com
username: admin
pw: pass4me

feel free to play with the site as much as you want even change the password so you know only you can log-in.
hopefully this will help debug the module.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

What's happening is that the jquery.translate plugin is not being loaded, and you're getting the error you mentioned in your original post. That's breaking javascript on the page, and that's why your fieldsets don't work.

And the reason is that you somehow have installed the module without the jquery.translate directory.
The GET to http://nikolian.com/sites/all/modules/translatableregions/jquery.transla... is getting a 404 error.

Basically, you somehow have installed a broken translatableregions module without the jquery.translate directory.

Please get a new package and install the whole thing.

vako’s picture

vako commented

The folder contains the jquery.translate directory, I also downloaded the dev version with the same results.
There are two files in that directory: jquery.translate-NCT,core,NCT-adapter,ui,progress,native.js & jquery.translate-NCT,core,NCT-adapter,ui,progress,native.min.js0000644

Should I download the jquery module from http://code.google.com/p/jquery-translate/downloads/detail?name=jquery.t...?

thanks!

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented

This is a problem with your webhosting or your process in deploying, it's nothing to do with the module.

The name of the file is
jquery.translate-NCT,core,NCT-adapter,ui,progress,native.min.js

On most webhosting environments this is case sensitive. You may have used some deployment technique where you lost the capital letters, or you may have an environment that can't use ','. Or you may have your webhosting environment set up funny to just not deal with that. But you'll have to figure out what it is.

When you can hit this URL
http://nikolian.com/sites/all/modules/translatableregions/jquery.transla...

And get a file instead of getting a 404, then you have your configuration issue fixed. Please post here when you figure it out. And please let me know what environment this is and how it got that way, because we don't want it to happen to anybody else.

vako’s picture

vako commented

I found the issue!

1. The download package has the file named as jquery.translate-NCT,core,NCT-adapter,ui,progress,native.min.js0000644 note the 0000644 at the end of the file name. I removed it manually.

2. The domain is not reachable without the www at the beginning of the domain name. So if you try http://www.nikolian.com/sites/all/modules/translatableregions/jquery.tra... it will work.

vako’s picture

vako commented

Just removing the trailing 0000644 from the file name solved the issue.

Thanks a lot for this great module. You may close the case.

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Status: Active » Fixed

There is no trailing 00000644 on the file name. You may be using a very unusual tool to unpack it. I recommend that you get a new tool (like tar), because that one's not working right.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.