Project

General

Profile

Actions

Bug #3341

closed

Clicking a confirmation link results in profile update trigger firing

Added by krileon over 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
12 March 2012
Due date:
% Done:

100%

Estimated time:
4:00 h

Description

This is due to the changes to the direct database functions now using triggers. However, in some cases the CB triggers need to be suppressed (like done to the activate function).


Files

3341-pt1.patch (812 Bytes) 3341-pt1.patch krileon, 10 April 2012 17:17
3341-pt2.patch (1.21 KB) 3341-pt2.patch krileon, 10 April 2012 17:17
3341-pt3.patch (1.39 KB) 3341-pt3.patch krileon, 10 April 2012 17:17
cb.tables.php (71.4 KB) cb.tables.php Pre-patched CB 1.8.1 file (includes #3314) krileon, 05 July 2012 20:15
controller.default.php (157 KB) controller.default.php Pre-patched CB 1.8.1 file krileon, 05 July 2012 20:15
comprofiler.php (66.4 KB) comprofiler.php Pre-patched CB 1.8.1 file krileon, 05 July 2012 20:15
comprofiler.class.php (202 KB) comprofiler.class.php Pre-patched CB 1.8.1 file from #3314 krileon, 05 July 2012 20:15

Related issues

Follows CB - Bug #3314: After update trigger fires after registrationClosedbeat05 March 2012

Actions
Actions #2

Updated by krileon over 9 years ago

Review all other usages of direct database functions and suppress their CB triggers if necessary.

Actions #3

Updated by krileon over 9 years ago

Patches fix all other locations to NOT fire the triggers (default behavior before this was implemented). Will require #3314 3314-pt1_rev1.patch before this fix does anything.

Actions #4

Updated by beat over 9 years ago

  • Target version changed from CB 1.8.1 to CB 1.9
Actions #5

Updated by c_schmitz over 9 years ago

Why was this moved to 1.8.2?
Since I am an professional member I would have expected that this would be treated with priority?

Actions #6

Updated by krileon over 9 years ago

It's not a critical issue. It was supposed to be in 1.8.1, but due to J2.5.5 breaking CB we had to do an emergency release with only the fixes needed to make CB stable again. Your subscription has no relevance to the priority of a ticket. You're welcome to apply the patches if you like.

Actions #7

Updated by c_schmitz over 9 years ago

How do you determine if it is a critical issue? It is a critical issue for me. Plugins were breaking because of this. I had to code around it and with more of my sites updating to the latest Joomla version and ran into this issue again. 4 months? You must be kidding.

Your marketing speak says
"
Get your professional support insurance policy now! Some solutions are just too important to leave on auto-pilot mode and if things go wrong they require immediate attention. This is where our Professional Support packages come into play. Sign-up to the package that best addresses your needs and keep our CB Team resources standby to address your issues as soon as they appear and before they cause you business impacting damage."

Yeah, right. Vaporware - that's what this is.

Actions #8

Updated by krileon over 9 years ago

We did address the issue. It's fixed right here in this ticket with 3 patches. We're doing the best we can with what time we have. I apologize if this is not efficient enough for you. We wish the release wasn't rushed, but we had no choice due to J2.5.5 making CB completely unusable. If that weren't the case this fix would've been there.

Please afford me a few minutes and I'll patch CB 1.8.1 for you and provide the pre-patched files attached to this ticket. You'd then only need to copy, paste, and replace on your install.

Actions #9

Updated by c_schmitz over 9 years ago

I understand the emergency situation with 1.81 and I am sorry for the pressure that this situation inflicted on you. This is mission-critical for me (otherwise I would not be this upset). Yes, patched files would be alot of help - thank you for coming forward with this proposal.

Actions #10

Updated by krileon over 9 years ago

The attached 4 files should resolve the issue entirely.

cb.tables.php
Location: administrator/components/com_comprofiler/library/cb/

comprofiler.php
Location: components/com_comprofiler/

controller.default.php
Location: administrator/components/com_comprofiler/controller/

comprofiler.class.php
Location: administrator/components/com_comprofiler/

Actions #11

Updated by beat about 9 years ago

  • Status changed from Resolved to Closed
  • Estimated time set to 4:00 h

Committed to SVN in r1886 for CB 1.9.
Thanks Kyle.

Actions

Also available in: Atom PDF