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 »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • solved: after upgrade from 3.3 to 3.4 error after push reportbutton in emailcamp
Pages: [1]

Author Topic: solved: after upgrade from 3.3 to 3.4 error after push reportbutton in emailcamp  (Read 1997 times)

MichaS.

  • I’m new here
  • *
  • Posts: 27
  • Karma: 0
  • CiviCRM version: 3.5.5
  • CMS version: Joomla 1.57
  • MySQL version: actual
  • PHP version: 5.x
solved: after upgrade from 3.3 to 3.4 error after push reportbutton in emailcamp
April 18, 2011, 04:36:16 pm
in the old version 3.3 its work fine, after update to 3.4 b3 all work fine without a detail.

When i push the "REPORT"-Button in the Area MAILINGS==> PLANED MAILINGS  i have follow errormessage:

Quote
Fatal error: Class 'JModuleHelper' not found in /var/www/vhosts/partnerbase.eu/httpdocs/joomla/administrator/templates/khepri/index.php on line 41
and a blank screen

All Reportslinks be defect but all other Links work fine and normal.

At the Moment i dont can show all informations about a mailcampaign ;-((

What ist the problem and what the solution for it?

See also the pic as attachment


Michael from de_DE
« Last Edit: May 21, 2011, 07:44:56 am by MichaS. »

Dave Greenberg

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 5760
  • Karma: 226
    • My CiviCRM Blog
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
April 19, 2011, 09:02:29 am
That error is about a Joomla class (JModuleHelper). You might want to search for more info via Google or the Joomla forums.
Protect your investment in CiviCRM by  becoming a Member!

MichaS.

  • I’m new here
  • *
  • Posts: 27
  • Karma: 0
  • CiviCRM version: 3.5.5
  • CMS version: Joomla 1.57
  • MySQL version: actual
  • PHP version: 5.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
April 19, 2011, 12:19:45 pm
Dear Dave,

thanks alot for your fast answer. I will research an read about this Joomlaclass...
But what i dont understood, why now after upgrade to 3.4?


Greetings from germany


Michael

MichaS.

  • I’m new here
  • *
  • Posts: 27
  • Karma: 0
  • CiviCRM version: 3.5.5
  • CMS version: Joomla 1.57
  • MySQL version: actual
  • PHP version: 5.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
April 26, 2011, 07:14:59 am
Its definitiv a problem from cicicrm not from the template, because i8n the new official Demosite from CIVICRM you can login in the BACKEND and find the same error!!!

Show here:

Quote
http://joomla.demo.civicrm.org/administrator/index.php?option=com_civicrm&task=civicrm/mailing/queue&reset=1

Its work fine in the old version and we need the reports veryx urgently to show, which partner receive our message.


PLEASE solve this BUG


Michael from de_DE

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
April 26, 2011, 02:24:39 pm
I spent some time (30+ mins) on this and could not figure out what changed and why. This has something to do with the use of the __autoload function in joomla and in use by some other civicrm packages also

Joomla 1.6 does the right thing and uses spl_autoload_register

We currently dont have a solution for J! 1.5. If you have the time and expertise would be great if you can investigate and fix. If not, please consider hiring someone to do the necessary work. Ping me on IRC and i can let you know where i got stuck

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

MichaS.

  • I’m new here
  • *
  • Posts: 27
  • Karma: 0
  • CiviCRM version: 3.5.5
  • CMS version: Joomla 1.57
  • MySQL version: actual
  • PHP version: 5.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
April 26, 2011, 02:30:59 pm
^Dear Donald,

thanks for your spenting time. i have small knowHow in php-programming and be not the right person. I will try to push the problem in a german forum and show on a good answer. But best for me and the solution of this problem is, do have detailed information what is the problem thats lost all data.

You write somethings about "spl_autoload_register" Experts knows whats means and work with this?


Michael from de_DE

kaixiong

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 3.4.x
  • CMS version: Joomla 1.5, Drupal 6, Drupal 7
  • MySQL version: MariaDB 5.1.x
  • PHP version: 5.2.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 19, 2011, 04:24:21 am
I managed to fix this for my Joomla 1.5 + CiviCRM 3.4.1 installation.

The root cause of this problem is the way the eZ package registers its autoload function ezcBase::autoload() in ezc/Base/ezc_bootstrap.php. Instead of adding this function to the autoload queue, eZ overrides Joomla's autoloader completely.

It goes like this:

1. Joomla defines a  __autoload() function in libraries/loader.php, activating class autoloading. This causes spl_autoload_functions() to return array('__autoload').

2. eZ detecting that autoloading is activated with spl_autoload_functions() !== FALSE, registers its autoloader ezcBase::autoload() with spl_autoload_register(). Unfortunately, because Joomla's __autoload() was not explicitly registered, it is erased and replaced by the registration.

It's a bit tricky to fix this because there seems to be no way to determine whether __autoload() was explicitly registered. So what I've done is to check if __autoload() continues to exist in the function queue after registering ezcBase::autoload(), and re-register it with spl_autoload_register().

Here's the replacement registration code for civicrm/packages/ezc/Base/ezc_bootstrap.php:

if ( spl_autoload_functions() !== false ) {
  spl_autoload_register(array('ezcBase', 'autoload'));

  // Re-register __autoload() if it wasn't explicitly registered
  if (function_exists("__autoload") && !in_array('__autoload', spl_autoload_functions())) {
    spl_autoload_register("__autoload");
  }
} elseif ( !function_exists("__autoload") ) {
  ...
}

--

This should work for all cases i.e. whether __autoload is defined and whether it is registered with spl_autoload_register().
« Last Edit: May 19, 2011, 04:26:25 am by kaixiong »

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 19, 2011, 06:49:09 am

i've patched 3.4.x a few days ago. Can u try this patch:

https://fisheye2.atlassian.com/changelog/CiviCRM?cs=34333

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

kaixiong

  • I’m new here
  • *
  • Posts: 2
  • Karma: 0
  • CiviCRM version: 3.4.x
  • CMS version: Joomla 1.5, Drupal 6, Drupal 7
  • MySQL version: MariaDB 5.1.x
  • PHP version: 5.2.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 19, 2011, 10:13:18 pm
The patch works for me, at least in fixing the CiviMail mailing report page.

I have to say, isn't the check for spl_autoload_register() a bit redundant since PHP5 is required?

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 20, 2011, 08:08:56 am

yes, but the downstream packages are both php4/php5 and we've tried to minimize the number of code changes we do to them

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

MichaS.

  • I’m new here
  • *
  • Posts: 27
  • Karma: 0
  • CiviCRM version: 3.5.5
  • CMS version: Joomla 1.57
  • MySQL version: actual
  • PHP version: 5.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 21, 2011, 06:56:06 am
Dear Donald,

how i can put in this patch into a working civicrm? I don't know the procedure...


Michael from germany

Donald Lobo

  • Administrator
  • I’m (like) Lobo ;)
  • *****
  • Posts: 15963
  • Karma: 470
    • CiviCRM site
  • CiviCRM version: 4.2+
  • CMS version: Drupal 7, Joomla 2.5+
  • MySQL version: 5.5.x
  • PHP version: 5.4.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 21, 2011, 07:26:53 am

http://en.wikipedia.org/wiki/Patch_%28Unix%29

or you can wait for the next release which will happen in 1-2 weeks

lobo
A new CiviCRM Q&A resource needs YOUR help to get started. Visit our StackExchange proposed site, sign up and vote on 5 questions

MichaS.

  • I’m new here
  • *
  • Posts: 27
  • Karma: 0
  • CiviCRM version: 3.5.5
  • CMS version: Joomla 1.57
  • MySQL version: actual
  • PHP version: 5.x
Re: after upgrade from 3.3 to 3.4 b3 error after push reportbutton in emailcampaign
May 21, 2011, 07:44:05 am
Dear Lobo,

i have change the code in the 2 files and puah there with ftp and it's work so fine..

Thanxs a lot. See the wtheterservice into berlin... the sun is shining so at the moment ;-)

Michael from de_DE

Pages: [1]
  • CiviCRM Community Forums (archive) »
  • Old sections (read-only, deprecated) »
  • Support »
  • Upgrading CiviCRM (Moderator: Deepak Srivastava) »
  • solved: after upgrade from 3.3 to 3.4 error after push reportbutton in emailcamp

This forum was archived on 2017-11-26.