I have recently un-installed all the related modules and updated to...

1) Drush make UI 6.x-1.4
2) Update feed api - CCK integration 6.x-1.3
3) Update feed api 6.x-1.3

When I 'Refresh update feeds, I now get a populated table: update_feed_api_project and that's a step forward - thanks for support on that.

HOWEVER, when I attempt to create a new Drush Makefile and type a module name e.g. 'autoload', I do not get any auto-complete action at ll - there is no 'spinner' and anything I type simply gets removed. I have tried this with a number of modules, includign those that I know are actually in the above table.

Also, when I go to view the View: '.../drush_makefile' I get the following errors...

"user warning: Unknown column 'field_module_ptype' in 'field list' query: SELECT vid AS _vid, delta as _delta, nid AS _nid, field_module_title AS title, field_module_server_key AS server_key, field_module_short_name AS short_name, field_module_api_version AS api_version, field_module_module_release AS module_release, field_module_ptype AS ptype FROM content_field_module WHERE vid IN (7,8,9,443,258,544,545,439,552,556) ORDER BY _nid ASC, _delta ASC in .../sites/all/modules/core/cck/includes/views/handlers/content_handler_field_multiple.inc on line 175."

I thought I was really there once I saw the table population but still no joy, any advice?

Comments

eugenmayer’s picture

sirclickalot’s picture

I was using the DEV version on do then, when that didn't work, I went back to 1.2.

sirclickalot’s picture

OK, I've gone to GitHub version and we're there, at least auto-complete-wise!

I can now at least add the first two of my modules from my long list: 'autoload' and 'ajax_load' with autocompletion working.
(only testing by trying these two at the moment for sanity)

HOWEVER...

1) When go to 'Add another' (multi-value) I get...

"warning: usort() [function.usort]: The argument should be an array in ...modules/update_feed_cck/update_feed_cck.formatter.inc on line 55.
warning: Invalid argument supplied for foreach() in ...modules/update_feed_cck/update_feed_cck.module on line 87."

2) When I go to Save a Drush makefile node I get...

"user warning: Unknown column 'field_module_ptype' in 'field list' query: INSERT INTO content_field_module (vid, nid, delta, field_module_title, field_module_server_key, field_module_short_name, field_module_api_version, field_module_module_release, field_module_ptype) VALUES (1901, 1872, 0, '', 'drupal_org', 'autoload', '6.x', '6.x-1.4', 'module') in .../modules/core/cck/content.module on line 1213.
user warning: Unknown column 'field_module_ptype' in 'field list' query: INSERT INTO content_field_module (vid, nid, delta, field_module_title, field_module_server_key, field_module_short_name, field_module_api_version, field_module_module_release, field_module_ptype) VALUES (1901, 1872, 1, '', 'drupal_org', 'ajax_load', '6.x', '6.x-1.3', 'module') in .../modules/core/cck/content.module on line 1213.
warning: usort() [function.usort]: The argument should be an array in .../modules/update_feed_cck/update_feed_cck.formatter.inc on line 55.
warning: Invalid argument supplied for foreach() in .../modules/update_feed_cck/update_feed_cck.module on line 87."

3) When I am viewing the previously saved node I notice that it says 'Packages(0)' and when I go to re-edit the previously saved Drush makefile node I get...

"warning: usort() [function.usort]: The argument should be an array in .../modules/update_feed_cck/update_feed_cck.formatter.inc on line 55.
warning: Invalid argument supplied for foreach() in .../modules/update_feed_cck/update_feed_cck.module on line 87."

..and neither of the two modules that I added are there.

We seem to be getting closer sir but I am at a bit of a loss as to why you are not seeing all these problems too - perhaps there is still a missing part of the jigsaw that I don't have in place.

I noticed that the GitHub version claims (via its .info file) to be 1.2.

I'm not sure that any other users will be able to spot that they have to sue the GitHUb version do it might be as well to update the do release ASAP so that they don't spend the many hours pulling hair that I have.

Thank you

eugenmayer’s picture

well autocomplete is not my project, and thats actually the issue with it, i cant simply release it. I guess i have to tighten iup the install notes.

for the other issues, i guess its because of my extensions to drush_make_ui which are not releases. Maybe the views got mixed and i have leftovers. I will install the modules on a fresh installation with a make file and publish that make file here. Lets see if we can get it work on a fresh drupal installation we both can test on.

In general, just to motivate you, i have those things up and running for over 6 months and we are using it in production on a day-regular base. So its working quiet well :)

sirclickalot’s picture

OK, I will install on a fresh local stack as soon as you upload something new.

BTW, the fields that are present in my 'content_field_module' table are...

vid, nid, delta, field_module_title, field_module_server_key, field_module_short_name, field_module_api_version, and field_module_module_release.

I notice that there is NOT a field 'field_module_ptype' which is certainly a cause of some of these failures.

eugenmayer’s picture

well that will then come down to:
- i fogot to update the scheme
- the scheme is not applied correctly
- or you have installed an old scheme

ptype is there for "project" type and is requiered, but it has been added "lately" to project .. let me have a look

sirclickalot’s picture

I already have a content type 'project' in my Drupal site - could that be the source of the problem!?

eugenmayer’s picture

Well no, you actually have to understand the architecture:

update_feed_api:
Just a source of projects / releases. Its used to ask questions like "what projects are or that server and what releases do i have"

update_feed_cck:
A cck field which has all fields to add packages based on the data fo update_feed_api. That field has an formatter to later be exported as entried os a make file. Generally you can add this cck field to every content_type

drush_make_ui:
Adds a view which actually can generate a complete make file with all needed fields, included core, version and allo this. Deeply basedon the modules before, just adds:
- a content type where update_feed_cck is a cck field (drush make file )
- that content type has some additional meta fields like "extra"

Your issue is most probably related to update_feed_cck. Please be sure you revert the drush_make_ui feature on every installation ( drush fr drush_make_ui).

sirclickalot’s picture

That's it! Reverted the Feature elements and I can now make makefiles.
Thank you so much for all your help over the latest couple of days, I will continue to post up any other strange behaviour that I find.

eugenmayer’s picture

Status: Active » Fixed

cool :)

sirclickalot’s picture

StatusFileSize
new15.73 KB
new4.9 KB

As promised, reporting anything I find that does not seem correct and, as before completely stuck on this one...

I've just tried to install on the clean site (local Acquia Drupal) and I know I've got all the module version correct.

However, after install and activating everything correctly and update the update feeds successfully, when I go to save a newly created Drush makefile node, I get...

"user warning: Table 'acquia_drupal.content_field_module' doesn't exist query: INSERT INTO content_field_module (vid, nid, delta, field_module_title, field_module_server_key, field_module_short_name, field_module_api_version, field_module_module_release, field_module_ptype) VALUES (1917, 1887, 0, '', 'drupal_org', 'pathauto', '6.x', '6.x-1.5', 'module') in C:\DEV6\sites\all\modules\core\cck\content.module on line 1213.
user warning: Table 'acquia_drupal.content_field_module' doesn't exist query: SELECT * FROM content_field_module WHERE vid = 1917 ORDER BY delta in C:\DEV6\sites\all\modules\core\cck\content.module on line 993.
warning: usort() [function.usort]: The argument should be an array in C:\DEV6\sites\all\modules\core\update_feed_cck\update_feed_cck.formatter.inc on line 55.
warning: Invalid argument supplied for foreach() in C:\DEV6\sites\all\modules\core\update_feed_cck\update_feed_cck.module on line 87."

...and later on next page visit...

"warning: usort() [function.usort]: The argument should be an array in C:\DEV6\sites\all\modules\core\update_feed_cck\update_feed_cck.formatter.inc on line 55.
warning: Invalid argument supplied for foreach() in C:\DEV6\sites\all\modules\core\update_feed_cck\update_feed_cck.module on line 87."

Everything really was clean and yet the table 'content_field_module' really does not exist in the database.

RE #8 fix when I had the same issue before, when I go to visit the Drush Make UI Feature (which appears to 'Need review' (screenshot 00.png) in order to 'revert' elements, it all appears to be correct as per the attached (screenshot 01.png).

Finally, Recreating the feature does not fix the problem.

Thank you

sirclickalot’s picture

Status: Fixed » Active

Just re-opened the above given the problem that I reported #11.

eugenmayer’s picture

Status: Active » Postponed (maintainer needs more info)

coming back to this one, iam not sure what is happening there. Rather looks like a features problem?

jrwilson’s picture

StatusFileSize
new200.03 KB

Load modules in the right location (../drushmakeui/sites/drushmakeui/modules) (maybe add admin_menu and module_filter) so they are accessible to modules administration page;

enable modules starting with dependancies until all of Drush make UI is enabled;

go to Update Feed API configuration @ http://drushmakeui/admin/settings/update_feed_api_settings select the Apis you want;

go to Refresh Update Feeds @ http://drushmakeui/admin/build/refresh_update_feeds (there are thousands of them and without that the autocomplete will not function;

at this point you should see Makefile in the left sidebar admin menu or go to http://drushmakeui/drush_makefile

I'm currently using it in Aegir. :)

sirclickalot’s picture

Issue summary: View changes
Status: Postponed (maintainer needs more info) » Closed (outdated)

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.