phpRecipeBook auto-complete issue

[wachuwamekil]

Hi all,

I seem to be having an issue with the most recent build of phpRecipeBook.

I am not able to add a recipe with auto-complete turned on, when I try i get the following error

"Ingredients cannot be entered more then once per recipe. Please combine the quantities or create a new recipe and list it as required recipe. Go back to fix the problem."

This is after selecting two different ingredients, I walked through the code, and disabled this check (commented it out), and it appears that with auto-complete turned on if I just type an ingredient in the filed it gets added as a null value in the db. So basically adding a recipe with one ingredient works, but if I add more than one ingredient it fails.

I was able to fix the issue by turning auto-complete off in the configuration file, but I really would like to use this feature if possible.

Just wondering if this is a new issue, or is it a bug that needs to be filed.

thx,

Ryan

[bigfoot65]

Hello,

Not sure as I have never heard about this issue until now. I would recommend you check the app web site to see if it has been identified as a bug.

If it is specific to the app, we may not be able to fix it. We can turn it off in the app install by default if that will help other users.

[lwoo]

Hello,

I am running into the same thing, what exactly did you do to fix this issue?

Thanks!

[bigfoot65]

This appears to be an app specific issue. Recommend you check the app home page and see if this bus has been identified. In the mean time, looks like the only way to work around it is via turning off that feature.

If I find anything out to correct it, I will post it.

[lwoo]

This appears to be an app specific issue. Recommend you check the app home page and see if this bus has been identified. In the mean time, looks like the only way to work around it is via turning off that feature.

If I find anything out to correct it, I will post it.

Understood, thanks.

Not sure where the config file for PHPRecipeBook is though or what file I need to modify to turn it off?


Thanks again,
lwoo

[lwoo]

Ok, figured out how to fix the issue.

For anyone else having this issue just change the following line:

$ajax_support = true;
to
$ajax_support = false;

In this file:

/var/hda/web-apps/recipebook/html/includes/config_inc.php

It seems that the developers at least know of the issue but not sure how much work is being done to resolve the issue.


lwoo

[bigfoot65]

Great job! We have modified the app accordingly to prevent this issue for future installs.

[lwoo]

Hate to bring up an old post but...

While researching an issue with the 'Shopping List' I found out that according to the bug tracker the ajax issue was fixed in the 2.5 release.

What does it take for the app to be updated in Amahi?

Is this something that is being worked on and if not is there a place to put in a formal request to update it?

[bigfoot65]

This update has been added to the list. The app web site indicates that 2.50 is an unstable release, so I need to test it before making the update. In response to your earlier post, this issue was corrected in the Amahi installer so it should not be a problem with new installs. Is this fix you posted now working?

I will work the update tonight and it should be ready for install tomorrow providing we feel it is stable. Keep in mind you will have to uninstall your current version, then reinstall to pick up the latest version. Part of the uninstall will include the Amahi autobackup feature, so any data will be backed up and imported on reinstall.

Thanks for pointing out the new update.

[lwoo]

Thanks for responding so quickly.

If I understood correctly the fix we did just disables the ajax piece but in the 2.5 release it works properly:

Will be fixed in release 2.50 (next release).


Date: 2009-08-22 18:17:06 UTC
Sender: nobody

It seems that the ajax is inadvertently adding in white space (a fair bit
of it too i think) before the ingredient id. So when the SQL statement is
formed, instead of having 'ingredient_id=5', for example, you have
'ingredient_id= 5'. This breaks the SQL statement and a whole load of
errors are thrown back.

I've experienced this problem using a Windows server, if that is any help
at all. I've not managed to track the bug down any further than that so
far.

Thanks again for the quick update.

lwoo