i have installed the acuatally dev version and add the content type field to my blog content type, my problem is the browese and clear buttons dont work when i click on them nothing happend and under this two buttons i have a 404 error message

i dont know where the problem is or what i did wrong, by the way reading your installation instruction is hard for not profi i tried my best to understand and bring this module to life on my testserver but i dont know why the buttons dont work and why i get this 404 error message under this buttons.

i hope you can help me

CommentFileSizeAuthor
#9 Bild 1.png18.11 KBkrobi
#4 Bild 1.png52.64 KBkrobi

Comments

gnindl’s picture

Assigned: Unassigned » gnindl
Status: Active » Postponed (maintainer needs more info)

If the buttons don't work there must be some problems with the JavaScript. Do you have the jquery_ui module plus a compatible jquery ui library, e. g. 1.6rc2, installed? See if the JavaScripts are correctly included on your edit page (View->Source) and if they are really there. Otherwise the JavaScript packaging may be corrupt, have a look at this thread:

http://drupal.org/node/369021

If this doesn't work have a look at the JavaScript error console and post the errors here.

Currently the dialog is rendered as an external html page. If this page cannot be found the '404 error' occurs. Can you view the page 'nodereference_explorer/table/selection_table.html' in an URL like
'http://localhost/sites/default/modules/nodereference_explorer/table/sele...'? Otherwise your installation is corrupt.

Cheers, Gottfried

krobi’s picture

Version: 6.x-1.x-dev » 6.x-1.0

ok now i have installed the jquery ui 1.6rc6 and now the buttons works but the 404 error is still here.

i cant reach the url with selection_table.html, whats wrong?

i now changed to release 1 from the dev version.

druth’s picture

I think there is an error in the jquery module code, I cannot get nodes to display in the nodeexplorer window no matter what i do, i have installed on a clean site with every version of jqeury.ui that i can find.... has anyone had any success? This looks great, just can't get any nodes listed...

krobi’s picture

Component: Code » User interface
StatusFileSize
new52.64 KB

i have a new problem, i have installed it on another server and new the buttons works but i cant really use it - see the screenshot.

gnindl’s picture

Looks like an Browser CSS problem. Which Browser and OS are you using (Safari & Mac?)? Have you tried it in Firefox 2/3? The CSS problem for the dialog has not been overcome yet (resulting in a weird layout). In version 1.1 you should be able to choose your own CSS.

gnindl’s picture

One more. Are the CSS added to your page? They are in the subfolder "dialog" called flora. They should be correctly referenced.

krobi’s picture

i use mac os 10.5.6 with all updates, i tried it with safari and firefox 3

this stylesheets are loaded
< link type="text/css" rel="stylesheet" media="all" href=" /sites/all/modules/nodereference_explorer/dialog/flora.all.css?j" />
< link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/nodereference_explorer/dialog/flora.dialog.css?j" />
< link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/nodereference_explorer/dialog/flora.resizable.css?j" />
< link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/nodereference_explorer/thickbox/thickbox.css?j" />

gnindl’s picture

Use JQuery UI Version 1.6rc2 that you can get at http://dev.jqueryui.com/changeset/2066/tags/1.6rc2?old_path=%2F&format=zip

That works fine for me. Jquery UI version 1.6rc6 is based on Jquery 1.3.1. I encountered a lot of JavaScript errors when using 1.6rc6 resulting in a 404 error, table not showing and a weird dialog layout (like on your screenshot).

I hope you have your drupal webapp deployed in the ROOT path, like http://localhost, and not in a subfolder, like http:localhost/drupal. This doesn' work yet, but in the next release.

krobi’s picture

StatusFileSize
new18.11 KB

hm now it looks like this

and now the buttons dont work at all :-(
strange, yes drupal is in the root of my web-server-account

krobi’s picture

ok now it works but the drop down is empty, seems to be a permission problem i have set all files to 777 and now it works.

but what is the problem with the empty drop-down menu?

gnindl’s picture

I think you have the same problem as this guy

http://drupal.org/node/372768

The cookies don't work.

gnindl’s picture

Status: Postponed (maintainer needs more info) » Needs work
IbnDrupal’s picture

I have the same problem but my drupal is in a subdirectory. Any short term fix for this (other than to move directory :p )

gnindl’s picture

- Go to table/js/selection_table.js and adapt the urls of the $.getJSON requests, e. g. "/nodereference_explorer/service_domain_name" -> "drupal/nodereference_explorer/service_domain_name"

- Go to nodereference_explorer.module line 6 and change the path of the variable "NODE_REFERENCE_SERVICE_NODE_DATA', e. g. 'nodereference_explorer/service_node_data' -> 'drupal/nodereference_explorer/service_node_data'

- Go to nodereference_explorer_widget.inc line 112 and adapt the path of the iframe src as above

I think that should work out, but look out for other hard coded paths in the code

pixelantegroup’s picture

I don't think that'll fix all the problems.

There are quite a few hard coded links in multiple places in this module that prevent it from being used unless your site is deployed in exactly the same manner as the module author's Drupal site he uses for developing the module.

The module really needs some sort of base url setting that's automatically derived from the Drupal installation (or hardcoded in ONE spot so that it can be changed easily), and which is then used everywhere else in the module code to create proper URLs for things.

gnindl’s picture

Version: 6.x-1.0 » 6.x-1.1-beta1
Status: Needs work » Fixed

This problem is obsolete in version 1.1 beta 1. Any Javascript JSON requests are not necessary any more due to the Views support

Status: Fixed » Closed (fixed)

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