Posted by 00ian on April 1, 2007 at 11:33am
| Project: | The Next Generation Integration |
| Version: | 5.x-1.x-dev |
| Component: | Miscellaneous |
| Category: | bug report |
| Priority: | normal |
| Assigned: | dixieau |
| Status: | closed (fixed) |
Issue Summary
When clean URL's are enabled the Drupal integration is broken almost completely.
Logins are no longer carried forward to TNG and there is no longer theme integration with TNG. The only thing which does work is that when a new user connects to TNG for the first time he is logged in and a new user is created in TNG. logging into TNG is now no longer possible, the only way in which I could connect to TNG was to delete all users from the TNG database.
In spite of this I will continue to use the module. It works very well. An excellent job!
| Attachment | Size |
|---|---|
| tng_error.txt | 1.71 KB |
Comments
#1
Same problem here. A pitty that this issue/your request is already from Arpil 1st without any reaction.
Who can solve this?
Without Clean URL's it works perfect, after switching on, in the Iframe starts the Drupal main page over and over again. When switching off again it works perfect again!
I'm also curious about further developments, like more user data transferred to TNG.
#2
I have only just finished setting this up on a development site and have it running on a live site both without any problems.
Out of curiosity did you enable clean urls AFTER installing tngintegrate or before?
#3
How strange! I can't figure out what I did first; switch on Clear URL and then install TNG or the other way around. What did you do and how could I fix this?
#4
I always enable clean urls immediately after creating my first user, that way there are never any conflicts. (Learnt that the hard way :()
Now for your problem, before we go any further can you confirm that you have checked your tng config.php to make sure that it is indeed showing the urls as clean? If so, then go back to your tng admin page and save it again just to make sure everything is updated with clean urls, then report back.
If that is not successful I will try and see if I can replicate your problem.
#5
Hi there,
first of all: Happy New Year! And thanks for your time and help.
I checked the tng config.php and it point to the right url. There's something else I configured at Drupal: Multilanguage - i18n
When I make a new menu item with the path ../tng, TNG shows up in the same windows (outside Drupal). When I change the path within the TNG module is show Page not found.
#6
Thank you and Happy New Year to you and all Drupalers.
Broes, I have disabled clean urls - it works, re-enabled clean urls and it works. The only thing I can think of and wonder is if you have named your tng directory /tng this always causes a problem, please refer to this post http://drupal.org/node/198303 and let me know if that solves your problems. If it doesn't then we might have to hang for the developer to respond as you have me baffled. One thing he will ask (so save time) is attach a snapshot of the tng settings page /admin/settings/tng
If you do need to change the directory name to something other than /tng/ remember to go into the tng directory and change it in the config.php, this will not update automatically (when I do this I make sure to access it externally and go through the readme.html and check that it is connecting to the database), make sure clean urls are enabled before you go back and adjust the settings again and click save.
Hope this solves the problem.
Cheers, Rhonda
#7
Hi Rhonda,
I fixed it!
After studying the TNG module code and behaviour of the site with the "Multilanguage - i18n" I discovered the following:
The i18n module adds something extras to the URL depending on the languages, for example without i18n it's: "www.example.com/?q=node/16. With i18n it becomes "www.example.com/?q=nl/node/16" (where nl is the countrycode for The Netherlands) or "www.example.com/nl/node/16" (when Clean URL is turned on).
In the TNG module I changed the URL to:
____
Path to TNG directory (include trailing slash): ../tng/
____
Then I turned Clean URL's on and it worked! So virtually the new Path steps back the /nl/ or /en/ background addition of the i18n module!
#8
broes, that is fantastic news! glad it's all working! Now to fiddle and enjoy..