This seems promising, so I tested your -dev of 11-jan-2010 on Drupal7.00.
Since the issue queue isn't that long yet, I'll just give all my feedback at once.

1. on page admin/structure/micro/add, I couldn't create a micro yet. After hitting the save-button this error appears:
"Fatal error: Cannot use object of type MicroType as array in C:\Damp\Sites\drupal-7.0\sites\all\modules\micro\micro.module on line 1323"
2. on page admin/structure/micro/add, a help-tekst for the Entity-field would be nice. Something like:
"The entity to which this micro will attach."
3. page admin/content/micro is left blank after a fresh install. Is this intentional? At least it is disturbing for the user.

Comments

johnv’s picture

I found one more thing. At times, i get the following message:
"Warning: call_user_func_array() [function.call-user-func-array]: First argument is expected to be a valid callback, 'micro_admin' was given in menu_execute_active_handler() (line 501 of ...\drupal-7.0\includes\menu.inc)."

blup’s picture

Hi johnv, thanks a lot for your input. The module is still in heavy development, so I apologize for the bugs. I'm hoping to have a stable release within a couple of weeks. Regarding your observations:

  1. Fixed.
  2. Fixed.
  3. No, this is not intentional. I'll be getting to this soon.
  4. Could you let me know on which pages you get the call_user_func_array() warning?
johnv’s picture

Thanks for your quick response.
4. 'Warning: call_user_func_array()" shows when you
A. go to Micro types >> Add >> Save (admin/structure/micro/add).
B. Show a node with micro's attached.
Only the first time. I don't know how to provoke the error another time - flushing caches doesn't work; restarting server does; un/reinstall too?

5. Please add the following line to micro.info-file. it will give you an extra link on page admin/modules/list.
configure = admin/structure/micro

johnv’s picture

6. A new micro type cannot be deleted. The following error after: create micro type ( append to node, no fields yet )>> Save >> Delete micro type.
"Recoverable fatal error: Argument 1 passed to micro_type_delete() must be an instance of MicroType, string given, called in micro.admin.inc on line 496 and defined in micro_type_delete() (line 1300 of micro.module).

johnv’s picture

StatusFileSize
new7.58 KB
new7.49 KB

7. Perhaps something to do with my server-settings & AJAX:
- Create a node, save
- Show node, add a micro with settings Display type = inline; Input type = Inline ==> OK
(I can only add, Delete button is not shown)
- Show node, add a micro with settings Display type = inline; Input type = Ajax_form ==> Error via global pop-up (see attachment)
(I can only add, Delete button is not shown)
- Show node, add a micro with settings Display type = inline; Input type = Ajax_flag ==> I can only Delete, no Create button
And when deleting the micro, global pop-up shows (see attachment 2)

8. If I attach a micro to a node, it comes at top pf the page. How can I influence the sort order? It would be nice if the micro-field shows up on the 'manage/display fields' tab.

9. If a micro is attached to none of the content types, it shows on ALL content types. This is good behaviour for some modules, but I doubt if micro should do so.

If you want me to create new issues, instead of appending this one, please tell me so.

aidanlis’s picture

Subscribe

blup’s picture

No, one thread is ok for the moment, and I appreciate the help with the bug finding. I am actually going to try and work heavily on the module this weekend, so hopefully by next week all of your bugs will be gone. Thanks again.

johnv’s picture

I tested your version of 15-jan. Here's a recap of the status:
Fixed = 1, 2, 5;
Fixed = 4 (call_user_func_array() warning)
Open = 3 (page admin/content/micro is left blank).
t.b.d. = 7 (ajax)
Open = 8 (sort order of micro field in Content type)
Open = 9 (attach to none or all)

ad 6: a new micro type can be deleted, but i get the following error message (I use entity.module -dev of 26-jan):

6A. I get this error when deleting a micro type:
PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '))' at line 1: DELETE FROM {micro} WHERE (mid IN ()) ; Array ( ) in EntityAPIController->delete() (line 399 of ..\modules\entity\includes\entity.controller.inc)

6B. I get this error when deleting a node. (It was connected to a microtype, but I don't know if this isrelevant.)
PDOException: SQLSTATE[42000]: Syntax error or access violation: 1064 You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ')) AND (base.eid = '10223')' at line 2: SELECT base.mid AS mid, base.mtid AS mtid, base.uid AS uid, base.eid AS eid, base.created AS created, mt.machine_name AS type FROM {micro} base INNER JOIN {micro_type} mt ON base.mtid = mt.mtid WHERE (base.mtid IN ()) AND (base.eid = :db_condition_placeholder_0) ; Array ( [:db_condition_placeholder_0] => 10223 ) in EntityAPIController->query() (line 154 of C:\Damp\Sites\hunkemoller.nl\sites\all\modules\entity\includes\entity.controller.inc).

tema’s picture

Subscribe.

kevinob11’s picture

Subscribe

BenK’s picture

Subscribing

Matthew Davidson’s picture

Okay, for the sake of my sanity I'm just going to assume that anything outstanding above has been addressed in the last few months worth of changes I've just pushed to d.o., or will be addressed in the course of completing #1477882: Roadmap to 1.0. Please let me know if you spot anything that remains unattended.

For the record, my strong personal preference is for one issue per issue node. ☺

Matthew Davidson’s picture

Status: Active » Fixed

Oh whoops, that means fixed, unless I hear otherwise.

Status: Fixed » Closed (fixed)

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