I tried to use d6 version and received this error message:
"An error occurred at /editablefields_html/6/field_example".
Module doesn't work :-(

Comments

johnthomas00’s picture

johnthomas00 commented

I had the same error.

markfoodyburton’s picture

markfoodyburton commented
Status: Active » Postponed (maintainer needs more info)

Thanks for the feedback, any chance of just a little bit more information?

Daniel A. Beilinson’s picture

Daniel A. Beilinson commented

When i set "editable" status to any cck field and create content with this field i have this error. In other words - always. :-)

Daniel A. Beilinson’s picture

Daniel A. Beilinson commented

And this message was created by ajax, because i see it in the floating window.

looplog’s picture

looplog commented

Same message here. Procedure followed:

Fresh d6.8 install
CCK 6.x.2.1
install editable fields 6.x.dev and ajax_load 1.1
create content type
add text field text area
display fields settings as editable
create content

drupal displays error message as above on page view

looplog’s picture

looplog commented

if it helps, firebug is reporting a 404 error in response to a call to example.com/editablefields.html/1/field_textest?
on page load, where textest is obviously my editable text area

looplog’s picture

looplog commented

again, I'm not sure how much it helps but the specific reponse from the request is:

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">

<html><head>

<title>404 Not Found</title>

</head><body>

<h1>Not Found</h1>

<p>The requested URL /index.php was not found on this server.</p>

<p>Additionally, a 404 Not Found

error was encountered while trying to use an ErrorDocument to handle the request.</p>
markfoodyburton’s picture

markfoodyburton commented

Hi, thanks for the info.
The only difference between your setup and mine omjn seems to be that your using CCK 6.x.2.1. Could you try using the -dev version of CCK?

(You will also need the latest version of ajax_load)

Please let me know one way of the other if this helps, if not, we'll dig more :-)

Cheers

Mark.

markfoodyburton’s picture

markfoodyburton commented

For the 404 error report - This is the editablefields that generates the 404 when it encounters an error - but normally it gives a helpful string with the error - the only case I've seen when that doesn't happen is when there is something fairly catastrophic - like a function isn't found - hence I'm wondering if the version of CCK is important.

Cheers

Mark.

looplog’s picture

looplog commented

hmm, the first time I tried the module was with a site based on the dec 6 dev version of CCK. I got the same result. I also tried the dev version of ajax_load to no avail, which is why I then built a minimal site with only release versions and the necessary modules to test editable fields. Whichever way, I've not gotten it to work...

markfoodyburton’s picture

markfoodyburton commented

Hi I've tried to replicate your error,and still haven't got anywhere :-(
For me, it works, almost no matter what I do!

Two things I thought of - but I'm almost sure neither can be a problem - but, just to confirm...
1/ Could you do a cache flush in drupal (under performace there's an option to flush the cache)
(I'm sure this wont make a difference, but ... you never know!)

2/ Can you confirm your using "clean URL's" - Actually, I tested this, and, although I expected the code to fail - it didn't !! - so - I'm fairly sure this isn't a problem, but - you never know !

Ill keep hunting, and trying to reproduce your failour, the fact that you get 'index.php not found' is - to put it mildly - strange!

Any more info woudl help!

Cheers

Mark.

markfoodyburton’s picture

markfoodyburton commented

could you confirm that there is a typo here- it should be editablefields_html (not '.' html)
if you really have a '.' then, thats the problem, but I can't find anything with a '.', so, I'm just not sure... (unless somebody, somewhere is replacing _html with .html, I guess thats possible, but it seems unlikely.... would be easy to change though :-) )

(err, what browser are you using?)

Cheers

Mark

Daniel A. Beilinson’s picture

Daniel A. Beilinson commented

I can give you my admin's login and password. What do you think?

markfoodyburton’s picture

markfoodyburton commented

I've just tried a totally fresh install - and I STILL can't get this to fail....
I have
content 6.x-2.x-dev
editablefields 6.x-1.x-dev
text 6.x-2.x-dev
ajaxload 6.x-1.1 (this may not be the best version, but for this test it is enough)

works out of the box for me :-(

Cheers

Mark.

looplog’s picture

looplog commented

yes it's a typo on my behalf - the actual error message has the underscore as you stated...

FYI: tested with Firefox 2.x and 3.0.x, as well as Konqueror, to the same effect.

CleanURLS are fine, that was one of the first things I checked...

markfoodyburton’s picture

markfoodyburton commented

OK, I still can't reproduce your error.
I took a clean drupal 6.8 install from the cvs, added cck, editablefields and ajax_load, and it worked a dream....

I tried on 2 different machines, (both have php5, but I'm sure thats not the issue)

open to ideas

Cheers

Mark.

looplog’s picture

looplog commented

Just to further eliminate, well, anyting at all really, I tried the ajax_load_example module available with the ajax_load dev version and that loads via ajax with with no problems. But still no luck with your module!

markfoodyburton’s picture

markfoodyburton commented

Yeah, you seem to be getting the error for things that dont need ajax_load anyway - like a normal text field!!!

if either of you ( La_ntegral or Omjn ) could give me a login - at least I could take a look.

BTW, are there any errors in your server log?

Cheers

Mark.

looplog’s picture

looplog commented

nothing very telling:

script '/srv/www/htdocs/index.php' not found or unable to stat

looplog’s picture

looplog commented

ok, so maybe it was telling. on a guess I moved my drupal install out of a subdirectory and put into the server root and presto bingo and walah it seems to work. I hope this has nothing to do with virtual hosts as I'm trying to get my head around those right now and am getting an aneurism as we speak!

looplog’s picture

looplog commented

This seems to be an issue with the rewrite rules in Drupal's default .htaccess file. By following:

  # Modify the RewriteBase if you are using Drupal in a subdirectory or in a
  # VirtualDocumentRoot and the rewrite rules are not working properly.
  # For example if your site is at http://example.com/drupal uncomment and
  # modify the following line:
  # RewriteBase /drupal

as stated in that file (!) I am able to make editablefields work for an installation in a subdirectory. Note that this only works when placing .htaccess in the server root directory. I presume one has to setup virtual hosts to have multiple subdirectory installations working?

looplog’s picture

looplog commented

Just so that you know, when not logged in, the error message produced is exactly the same, which is not very user friendly.

Thanks for the response, by the way... (oh, and the module, it looks and works great when it finally does work)

markfoodyburton’s picture

markfoodyburton commented

omjn, can you try the version in the head of the DRUPAL-6--1 branch direct from CVS... I have changed the call back address in the javascript from /editablefields_submit/.... to ?q=/editablefields_submit/... (and same for _html)
I suspect this will work better on a site setup as you had - not sure - but hope so !

If it does work (without the modifications you had to make), then I'll release it as a new version.

cheers

Mark.

johnthomas00’s picture

johnthomas00 commented

This fixed mine.

looplog’s picture

looplog commented

Yup it seems to work on my basic 6.8 install. It doesn't appear to be working on an older 6.6 install but that could be for other reasons. I won't have much time until the w/e to look in more detail.

markfoodyburton’s picture

markfoodyburton commented
Status: Postponed (maintainer needs more info) » Fixed

Thanks, (The current dev release has the fix in it now), and mark this as closed for now.

Thanks for the help tracking this down

Cheers

Mark.

Status: Fixed » Closed (fixed)

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