CiviCRM Community Forums (archive)

*

News:

Have a question about CiviCRM?
Get it answered quickly at the new
CiviCRM Stack Exchange Q+A site

This forum was archived on 25 November 2017. Learn more.
How to get involved.
What to do if you think you've found a bug.



  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Civievent max participant number cannot be changed after event has been created
Pages: [1]

Author Topic: Civievent max participant number cannot be changed after event has been created  (Read 328 times)

greenitcompany

  • I’m new here
  • *
  • Posts: 10
  • Karma: 0
  • CiviCRM version: 4.3.3 and 4.2
  • CMS version: Drupal 6.28 & 7.22
  • MySQL version: MySQL 5.1
  • PHP version: PHP 5.3.2
Civievent max participant number cannot be changed after event has been created
January 30, 2015, 03:38:46 am
Just wondering whether anyone has come across this before? I have found no mention of this in the forum, documentation or on the web. So it may be a rarity or something isolated to this clients installation. This installation has also been updated to the latest 4.5.5 version so all files are new and the database has been updated. Very odd!

Anyone experienced this problem before and if so what was your solution?

Thanks in advance,

Adam

joanne

  • Administrator
  • Ask me questions
  • *****
  • Posts: 852
  • Karma: 83
  • CiviCRM version: 4.4.16
  • CMS version: Drupal 7
Re: Civievent max participant number cannot be changed after event has been created
January 30, 2015, 05:05:51 am
Is this problem reproducible on our demo site? http://d45.demo.civicrm.org/

greenitcompany

  • I’m new here
  • *
  • Posts: 10
  • Karma: 0
  • CiviCRM version: 4.3.3 and 4.2
  • CMS version: Drupal 6.28 & 7.22
  • MySQL version: MySQL 5.1
  • PHP version: PHP 5.3.2
Re: Civievent max participant number cannot be changed after event has been created
January 30, 2015, 07:06:43 am
Hi Joanne, thanks for your response.

Nope, it works fine on your demo site.

The problem is that the change is accepted and processed when pressing save. But there is no save dialogue box that pops up to tell me the setting has been saved. Which is concerning as changes to contacts or other civicrm aside from CiviEvent are accepted and the dialogue box is briefly displayed as it should. I'll re-check the permissions, but I've not changed any and I don't think my client has. You would normally also get a permissions issue displayed if a change is not allowed with your current assigned role permissions.

Adam

greenitcompany

  • I’m new here
  • *
  • Posts: 10
  • Karma: 0
  • CiviCRM version: 4.3.3 and 4.2
  • CMS version: Drupal 6.28 & 7.22
  • MySQL version: MySQL 5.1
  • PHP version: PHP 5.3.2
Re: Civievent max participant number cannot be changed after event has been created
January 30, 2015, 07:24:42 am
This problem only occurs on existing events.

If I create a new event I can edit the event no problem and change the participant number as many times as i like. I even tested it with a registered participant just in case CiviCRM stopped the participant number being changed once there were registered attendees.


joanne

  • Administrator
  • Ask me questions
  • *****
  • Posts: 852
  • Karma: 83
  • CiviCRM version: 4.4.16
  • CMS version: Drupal 7
Re: Civievent max participant number cannot be changed after event has been created
January 30, 2015, 02:29:24 pm
I am not a techie, but if it was me, I would be opening phpmyadmin and comparing the fields for a new event without the problem and an old event with the problem in the event table looking for a difference of some kind such as hidden characters or blanks instead of nulls etc.   


Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Using CiviCRM »
  • Using CiviEvent (Moderator: Yashodha Chaku) »
  • Civievent max participant number cannot be changed after event has been created

This forum was archived on 2017-11-26.