Help,

When enabling the CVS under 4.7, my TinyMCS and "Image module", are missing from my "Create page/story/image/video" pages, Disabling the I18N module makes the links work again.

Anyone tried this???

Comments

belio’s picture

Did you adjust the visibility settings in your tinymce profile?

By default only things like "node/*" are there; with i18n active, you need to add "en/node/*" f.i.

jmiccolis’s picture

belio, thanks for the tip. This was driving me crazy - but adding the language codes to paths worked perfectly.

pancapangrawit’s picture

I had the same problem and found this is relevant to any "block"-definition. I restrict the appearance of some blocks to the frontpage by using - this also doesn't work - what would I have to write insteda?
Thanks for any advice.
Best
.r.

pancapangrawit’s picture

Sorry, I just wrote rubbish, I guess, and I can't delete it any more. What I found is simply that page-visibility-settings of blocks don't seem to stick any more - but I'm not even sure at the moment, whether this is because of the i18n-module - it might have to do with organic-groups as well, which I am also experimenting with at the moment.
Thanks for the en/node/* tip anyways.
Best
.r.

pancapangrawit’s picture

Sorry for continuing again - but things get a bit clearer now. It does seem to have to do with i18n. I tried to define a multilingual block in the hope to bypass the problem. There I get this message twice:

warning: Invalid argument supplied for foreach() in /dataraid/www/modules/i18n/contrib/i18nblocks.module on line 79.

Nevertheless the multilingual block can be saved and is operational. Yet the page-visibility-settings nevertheless don't stick/don't get saved.

Best
.r.

klance’s picture

The first time I installed TinyMCE (4.7) and I18N (cvs) in 4.7, I installed I18N first and then TinyMCE. When installed in this order, I was able to click on Administer -> Settings -> TinyMCE, but couldn't configure TinyMCE because it did not display a "Create profile" link. And that was it; I couldn't do anything to get TinyMCE rolling after that. I tried to disable I18N and remove them both, but TinyMCE continued to hide its profiles, so I wiped my entire Drupal installation and started from scratch. When installed in reverse order--TinyMCE first and then I18N--it seemed to work fine, as long as I remembered to add en/node/* etc. to my visibility settings as belio mentioned above.

pepeek’s picture

things like "node/*" with i18n active, you need to add "en/node/*" are a bit painful if you have many languages. Also the maintainance is a pain - once you add new language, then you must remember to update the settings.

Is there a way to set something like "??/node/*", or better "<LANG>/node/*", or is there a better approach to make this work automaticaly instead of the manual all-language-prefix-listings?

pepeek’s picture

Title: I18N and image module/TinyMCS » Works fine with drupal 4.6

BTW, this behaves fine under 4.6 so there must be a way to achieve this...

jose reyero’s picture

Title: Works fine with drupal 4.6 » Compatibility problem with TinyMCS and Image module
Priority: Normal » Minor
Carlos Miranda Levy’s picture

I did */node/* and it worked fine for me...

jose reyero’s picture

Category: bug » support
Status: Active » Fixed

I have TinyMCE and i18n working with no major issues, so AFAIK this should be fixed.

Feel free to reopen (and specify version of all modules if not, no more support for 4.6 btw)

Anonymous’s picture

Status: Fixed » Closed (fixed)

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