Author Topic: V1.9 alpha 11640 feedback (Read 7429 times)

msn · September 28, 2007, 12:43:37 pm

I followed the development of CiviCRM1.9 in the issue tracker and dev.group: I want to compliment the development team for the implementation of new issues, upgrades and the fastnes of publishing the release!

I updated my 1.8 test configuration to 1.9 (including db update) and have my first feedback:

a: In group setting the box Group type is not present (new and edit group)
b: In Send Mailing the Mailing Recipients are not shown (because of a?)
c: When pressing the Previous button in step 1 of send mail (mailing name) an error tekst is shown, asking for the mailing name. I would aspect to go to civicrm/mailing, like pressing the Cancel button.
d: When pressing re-use of a mailing (old mailing from v1.8 ) an error comes up: 'Sorry. A non-recoverable error has occurred. You do not have permission to access this mailing report Return to home page.'

I cannot test this in a public sandbox yet, I think I am a litle bit early .....

Donald Lobo · September 28, 2007, 07:01:49 pm

a/b: Not sure what you mean by the box "group type" is not present. Can you compare your screen with the same screen on sandbox. If the group type has no checkboxes, can u run the following query:

select v.* from civicrm_option_value v, civicrm_option_group g where v.option_group_id = g.id and g.name = 'group_type';

You should see 2 records (Access Control, Mailing List)

c: I've fixed the code. the Previous button should not be on the first page

d. Are you on drupal or joomla? If on drupal, are you running as the admin user?

lobo

msn · September 28, 2007, 07:35:32 pm

a/b: I am missing in creating new group (and editing group) the boxes and text 'Acces Control' and 'Mailing List' in the Group Type setup.

The query gives no records:

Code: [Select]

MySQL returned an empty result set (i.e. zero rows).

When I run the query upgrade 1.8->1.9 for civicrm_option_group and civicrm_option_value :

Code: [Select]

INSERT INTO `civicrm_option_group` (`domain_id`, `name`, `description`, `is_reserved`, `is_active`) 
	VALUES  
	      (@domain_id, 'group_type', 'Group Type', 0, 1);
	

	SELECT @option_group_id_gtype := max(id) from civicrm_option_group where name = 'group_type';
	SELECT @option_group_id_adOpt := max(id) from civicrm_option_group where name = '';

	INSERT INTO 
	   civicrm_option_value (option_group_id, label, value, name, grouping, filter, is_default, weight, description, is_optgroup, is_reserved, is_active) 
	VALUES
	  (@option_group_id_gType, 'Access Control'  , 1, NULL, NULL, 0, NULL, 1, NULL, 0, 1, 1 ),
	  (@option_group_id_gType, 'Mailing List'    , 2, NULL, NULL, 0, NULL, 2, NULL, 0, 1, 1 );

mysql responds with

Code: [Select]

Error
SQL query: 
INSERT INTO `civicrm_option_group` ( `domain_id` , `name` , `description` , `is_reserved` , `is_active` ) 
VALUES ( 
@domain_id , 'group_type', 'Group Type', 0, 1);

MySQL said:  FPRIVATE "TYPE=PICT;ALT=Documentation" 
#1048 - Column 'domain_id' cannot be null

d: I am logged in as Drupal user 1 (admin)

Donald Lobo · September 28, 2007, 07:47:28 pm

At the very top of the file there is:

SELECT @domain_id := id from civicrm_domain;

which sets the domain_id, so not sure why you are getting those errors. Can you investigate and figure out why you are getting the below errors. Please report back to the forum of the cause and fix. I suspect item d in your list is also related to this. Once you have this working, you might want to mark all group types for their intended use

lobo

msn · September 28, 2007, 08:06:52 pm

I am not an expert coder but I will do my best.
I will come back with cause, fix or questions....

msn · September 28, 2007, 10:18:10 pm

In de database civicrm_option_value is not set by the upgrade script. I made the settings by hand and it worked.

I think the problem is in the name of the variable:

SELECT @domain_id := id from civicrm_domain;
   INSERT INTO `civicrm_option_group` (`domain_id`, `name`, `description`, `is_reserved`, `is_active`)
   VALUES
     (@domain_id, 'group_type', 'Group Type', 0, 1);


   SELECT @option_group_id_gtype := max(id) from civicrm_option_group where name = 'group_type';
   SELECT @option_group_id_adOpt := max(id) from civicrm_option_group where name = '';

   INSERT INTO
     civicrm_option_value (option_group_id, label, value, name, grouping, filter, is_default, weight, description, is_optgroup, is_reserved, is_active)
   VALUES
     (@option_group_id_gType, 'Access Control' , 1, NULL, NULL, 0, NULL, 1, NULL, 0, 1, 1 ),
     (@option_group_id_gType, 'Mailing List' , 2, NULL, NULL, 0, NULL, 2, NULL, 0, 1, 1 );

msn · September 29, 2007, 05:14:11 am

The issues a,b,c and d are solved by changing the variable gType to gtype.

My next issue is:
e:

Testing the mailing feature I noticed that mails are not send, they stay 'scheduled'. I override cron with the command:
http://www.domain.org/drupaltest/sites/all/modules/civicrm/bin/civimail.cronjob.php?name=aaa&pass=bbb

I know that domain, name and pass are the same as the 'old' workin CiviCRM1.8 version. Name and pass are equal with my drupal no 1 admin account.

civimail.cronjob.php gives the error:
Fatal error: session_start() [<a href='function.session-start'>function.session-start</a>]: Failed to initialize storage module: user (path: ) in /home/domain/public_html/drupaltest/sites/all/modules/civicrm/bin/civimail.cronjob.php on line 43

nessumsara · October 01, 2007, 05:45:14 pm

Quote from: msn on September 29, 2007, 05:14:11 am

The issues a,b,c and d are solved by changing the variable gType to gtype.

Can you please explain how one makes this change? I'm having the same problem with not being able to see the mailing recipient options.

Donald Lobo · October 01, 2007, 07:10:32 pm

argh

Thats a stupid typo to have. Thanx for tracking it down. This will be fixed in the next alpha/beta release

For your session issue below, ensure that

session.save_handler = files

in your php.ini. It is currently set to 'user' and civicrm does not provide session handlers (drupal/joomla take care of taht for us)

lobo

nessumsara · October 01, 2007, 08:12:08 pm

I tried re-applying the script listed above, changing gType to gtype. I received the following error.

Code: [Select]

Error

SQL query:

INSERT INTO `civicrm_option_group` ( `domain_id` , `name` , `description` , `is_reserved` , `is_active` )
VALUES (
@domain_id , 'group_type', 'Group Type', 0, 1
);

MySQL said: Documentation
#1062 - Duplicate entry 'group_type-1' for key 2

Can you provide instructions for making the change manually using phpMyAdmin or am I just going to have to wait until the next alpha update before I can test out the new mailing process in 1.9?

Donald Lobo · October 01, 2007, 09:09:29 pm

You might want to wait for the next 1.9 release. either way you will need to start from your 1.8 database.

you have to change gType to gtype in the upgrade file

lobo

nessumsara · October 01, 2007, 10:03:55 pm

hmmm. the civicrm tables are all part of my larger Joomla database. I've already started making updates to that, so can't go back to the database I was using before I upgraded to 1.9. Will there be any way to avoid having to go back to my 1.8 database? Perhaps you could add a script to go from 1.9 to 1.9. Otherwise I'm screwed.

Donald Lobo · October 01, 2007, 10:56:27 pm

all our upgrade instructions ask you to experiment with a copy of your database and not the live database itself. We do not plan to have a 1.9 -> 1.9 upgrade script. Note that 1.9 is still in alpha and schema changes are possible. We freeze the schema at the beta stage

Your upgrade issue can be resolved by someone familiar with mysql. Please enlist the help of a local mysql person

lobo

nessumsara · October 02, 2007, 09:56:01 am

You're right. I got all excited about the new features and didn't test it out on a sample database. So should I wait until you have a new alpha or a beta version before I have a mysql person fix my database or should I have them try to fix the gType vs. gtype problem now?

Dave Greenberg · October 02, 2007, 10:08:57 am

Best option is if you can get help to rollback to 1.8 without losing important constituent data. This assumes you have a recent backup. Then wait for the beta or final release to upgrade (again, keeping a copy).

If this is not possible and you can just wait for beta or final with the DB in it's current state, I guess I would do that. As Lobo mentioned we don't provide 1.9x to 1.9y upgrade scripts - so waiting will save you from the possibility of addtional hassles.

CiviCRM Community Forums (archive)

News:

Author Topic: V1.9 alpha 11640 feedback (Read 7429 times)

msn

V1.9 alpha 11640 feedback

Donald Lobo

Re: V1.9 alpa 11640 feedback

msn

Re: V1.9 alpa 11640 feedback

Donald Lobo

Re: V1.9 alpa 11640 feedback

msn

Re: V1.9 alpha 11640 feedback

msn

Re: V1.9 alpha 11640 feedback

msn

Re: V1.9 alpha 11640 feedback

nessumsara

Re: V1.9 alpha 11640 feedback

Donald Lobo

Re: V1.9 alpha 11640 feedback

nessumsara

Re: V1.9 alpha 11640 feedback

Donald Lobo

Re: V1.9 alpha 11640 feedback

nessumsara

Re: V1.9 alpha 11640 feedback

Donald Lobo

Re: V1.9 alpha 11640 feedback

nessumsara

Re: V1.9 alpha 11640 feedback

Dave Greenberg

Re: V1.9 alpha 11640 feedback