It took me a while to find out why my drag&drop and some js-based tools, such as views with java-script enabled didn't work any more. There were no bugs reported. After disabling some supisious modules, I found out that translatableregions were the reason behind. After disabling the module everything works fine again. So there must be any were a js-bug inside this module ...

Comments

rfay’s picture

rfay
he,him
Primary language English
Location Palisade, CO, USA
commented
Assigned: choy » Unassigned

@ChoY please say *what* module is disrupted by translatableregions and give a step-by-step recipe for demonstrating the problem. Thanks!

choy’s picture

choy commented

There is no specific module disrupted, it is moreover a general disrupture, I observed on following points:
Drag&Drop as used in a lot of D7-admin pages didn't worked anymore - it was possible to draf&drop, but after saving, all was set back in the previous position. It has to be enabled the weight to to rank positions.
The edition of subpoints in the views module (usually by opening a javascript window) resulted instead in a request for download a js-plugin. - I had to disable javcascript in views advanced settings, to make thing work again.
The content type manage display let either by drag & drop or by format field options switch fields from hideen to visible and vice versa - this also was no more possible.
I had no error message no warning about what it could be, only the suspect, that there must be a conflict with a module - which was revealed finally tranatableregions after disabling one after an other of supicious candidates using javascript. My translatableregions was as default + the activated button view block. For my personal (user-1) acccount, I had the translatikon button disabled. By default it was enabled to all users.
The described disrupture occured with all kind of browsers and OS.
I hope this may help you to find the bug, of this very useful module for our babylonic world of languages ...

rfay’s picture

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

I just tried this with the blocks page and had no trouble. In D7, I went to the blocks page and rearranged blocks in a region.

Have you tried this on a clean D7 install to see if it's just translatableregions that is the issue?

Thanks for being a loyal user! Great to have feedback from you.

choy’s picture

choy commented

no I I didn't tried it yet on a clean D7 - but if it worked well in your case, it should be the same in my case ...
It may be as well possible that the bug comes up if translatableregions + some additional $module are installed.
try it out with views dev-version module added to your clean D7 - it was so far the only added module, where the bug came up. The other bugs where all linked to D7 core ..
(the current stable views version is buggy, that's why I prefer to work with views dev.)

choy’s picture

choy commented

Could you find out in between why tranlatableregions cause so much trouble to Ajax? In between I could a bug with taxonomy manager (didn't displayed the edit part of a term) has its roots in the translatable regions. Since I unsinstalled also te taxonomy manager works well again. I would really like to use the translatable regions module, but before this bug isn't fixed, it stays unusable to me - sorry. Good luck in finding the bug ...

rfay’s picture

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

I won't even look at this again until somebody provides a step-by-step recipe explaining how to recreate the problem. As I said I was unable to reproduce it.