Account Manager Page giving error after 4.14.1 upgrade

Squiz Matrix Support
1

We just upgraded to 4.14.1 and now, when users are trying to signup for an account using an Account Manager Page asset they get the error:

 

Undefined index: confirm_field

 

 

Strange thing is, I have a trigger setup for when a new user signs up. And, I am getting those emails, with an asset ID, but when searching for the asset id, it isn't found.

 

Any ideas what is going on?

2

We just upgraded to 4.14.1 and now, when users are trying to signup for an account using an Account Manager Page asset they get the error:

 

 

 

Strange thing is, I have a trigger setup for when a new user signs up. And, I am getting those emails, with an asset ID, but when searching for the asset id, it isn't found.

 

Any ideas what is going on?

 

Hi Nic,

Can't find a reference to that index in the obvious places I checked. 

Does it, in the error.log, point exactly where the error is being generated?

 

Can you look for that assetid in the DB directly? like in the sq_ast or sq_ast_lnk table?

 

Ash

3

 

Hi Nic,

Can't find a reference to that index in the obvious places I checked. 

Does it, in the error.log, point exactly where the error is being generated?

 

Can you look for that assetid in the DB directly? like in the sq_ast or sq_ast_lnk table?

 

Ash

 

I am not good with DB stuff. how would I do that? This is what I tried and didn't work:

SELECT * FROM sq_ast WHERE id=111185;
4

Below are the few queries that might help:

SELECT * FROM sq_ast WHERE assetid='111185';

SELECT * FROM sq_ast_lnk WHERE minorid=‘111185’;


SELECT * FROM sq_ast_attr_val WHERE assetid=‘111185’;

Any news about the error apperance in the error.log? In 4.14 I think Matrix should be specifying the file and the line number where the error is happening.

 

Ash

5

Below are the few queries that might help:

SELECT * FROM sq_ast WHERE assetid='111185';

SELECT * FROM sq_ast_lnk WHERE minorid=‘111185’;


SELECT * FROM sq_ast_attr_val WHERE assetid=‘111185’;

Any news about the error apperance in the error.log? In 4.14 I think Matrix should be specifying the file and the line number where the error is happening.

 

This is all that is in the logs:

 

  14:58:35 - 07 May
User: Public User (7)
Level: PHP Notice 

			<span style="font-family:'Courier New', Courier, monospace;">(/packages/cms/page_templates/page_asset_builder/page_asset_builder.inc:589) - Undefined index: confirm_field</span>
	
			14:59:29 - 07 May<br>
			User:&#160;<strong>Public User</strong>&#160;(7)<br>
			Level:&#160;<strong>PHP Notice</strong>
		
			<span style="font-family:'Courier New', Courier, monospace;">(/packages/cms/page_templates/page_asset_builder/page_asset_builder.inc:589) - Undefined index: confirm_field</span>
	<p>&#160;<p>Running those queries just show 0 rows. So looks like it can't find it.</p>
6

Another thing. In the Create Form Layout, we have the %details-F_password% keyword. But that keyword is not shown when looking at the print_limbo_keywords.php page for Account Manager Page.

 

I am assuming the error has something to do with the password field.

7

Yeah looks like that. 

Around the file/line you pointed it seems like Matrix is trying to process the value of the attributes for the asset created.

 

Is the password field being printed on the page? also is the confirm password field printed?

 

Looks like Matrix is trying to look at the 'Confirm Password' field and not finding it in the POST.

 

Ash

8

Yeah looks like that. 

Around the file/line you pointed it seems like Matrix is trying to process the value of the attributes for the asset created.

 

Is the password field being printed on the page? also is the confirm password field printed?

 

Looks like Matrix is trying to look at the 'Confirm Password' field and not finding it in the POST.

 

Yeah, the password and confirm fields are being printed. The page is here:

 

http://www.puc.edu/puc-life/marketplace/register

9

Hmmm.

Not quite sure what is happening there. Looks like Matrix is looking for some value in POST and not finding it. Can't pin Point it to where exactly though.

May be try to remove the password field and add it back?  

Having a quick looks, its doesn't seem like much have changed in password field or in Account Manager Page for some time now.

What version was it upgrade from?

 

Ash

10

Hmmm.

Not quite sure what is happening there. Looks like Matrix is looking for some value in POST and not finding it. Can't pin Point it to where exactly though.

May be try to remove the password field and add it back?  

Having a quick looks, its doesn't seem like much have changed in password field or in Account Manager Page for some time now.

What version was it upgrade from?

 

Yeah, removing then adding it back didn't seem to help.

 

We upgrading from 4.12.1 to 4.14.1. Today we are upgrading to 4.14.2 so we will see how it works after that.

11

Strange thing is, I have a trigger setup for when a new user signs up. And, I am getting those emails, with an asset ID, but when searching for the asset id, it isn't found.

 

Tried recommitting the trigger? Failing that disabling it? If the trigger bombs out it's probably taking the rest of the signup process with it. I had something similar happen the other week after we upgraded to 4.14.1.

12

 

Tried recommitting the trigger? Failing that disabling it? If the trigger bombs out it's probably taking the rest of the signup process with it. I had something similar happen the other week after we upgraded to 4.14.1.

 

I don't see how it could be a trigger issue. It is errors on the form that are preventing the user from continuing. 

 

I might just have to recreate the form and see if that fixes it.

13

Apparently this issue is identified as a new bug, #6325 Assets, like Page Account manager, using password field for sign up throw "undefined index: confirm_field" error.

 

Stay tuned for further updates and fixed!

 

Ash

14

Apparently this issue is identified as a new bug, #6325 Assets, like Page Account manager, using password field for sign up throw "undefined index: confirm_field" error.

 

Stay tuned for further updates and fixed!

 

Ash

 

Thanks!

15

Apparently this issue is identified as a new bug, #6325 Assets, like Page Account manager, using password field for sign up throw "undefined index: confirm_field" error.

 

Stay tuned for further updates and fixed!

 

Ash

 

Hi guys,

 

I've been running 4.14.1 since release and don't encounter this bug, I use raw HTML to write the form. Until you upgrade, try manually entering the input fields (copy the HTML from the printed page) to maybe get past the bug if it's stopping new users signing up.

 

Jeremy

 

Edit: demo

16

 

I've been running 4.14.1 since release and don't encounter this bug, I use raw HTML to write the form. Until you upgrade, try manually entering the input fields (copy the HTML from the printed page) to maybe get past the bug if it's stopping new users signing up.

 

This is a 4.14.2 bug ( http://bugs.matrix.squiz.net/view_bug.php?bug_id=6325 ). Pasting in the output of a keyword is not a good idea in my opinion. That can break things later.

17

This is a 4.14.2 bug ( http://bugs.matrix.squiz.net/view_bug.php?bug_id=6325 ). Pasting in the output of a keyword is not a good idea in my opinion. That can break things later.

I’m confused, is 4.14.1 not affected then?


Manually entering fields vs. keywords has always been my accessible/control hack for Matrix; as far as I can see it shouldn’t cause issues, particularly for form fields as Matrix only needs a field name and val, but now with the accessible field options built into 4.14.2 (I think, thanks Squiz :D) it can hopefully be an outgoing method.

18

I'm confused, is 4.14.1 not affected then?
Manually entering fields vs. keywords has always been my accessible/control hack for Matrix; as far as I can see it shouldn't cause issues, particularly for form fields as Matrix only needs a field name and val, but now with the accessible field options built into 4.14.2 (I think, thanks Squiz :D) it can hopefully be an outgoing method.

 

No, it shouldn't affect 4.14.1.

 

I can understand manually entering keyword output in a controlled environment, which I have done, but I still would advise not using pasted output rather than a keyword. #1 reason for me, and to stress to users is if you are using keywords and a custom bodycopy, you can clone the form and Matrix will rewrite all of the keywords. If those were all just pasted in input fields, you would have to do all of them manually, which would be a huge pain.

 

Agree that the new accessible option is great!

19

Yes in installations with multiple people using the admin interface I agree that keywords are the way.

Can’t wait to take it for a spin, but might hold off upgrading then until this little bug is squashed.

20

Apparently this issue is identified as a new bug, #6325 Assets, like Page Account manager, using password field for sign up throw "undefined index: confirm_field" error.

 

Stay tuned for further updates and fixed!

 

Ash

 

Do you have a link to the patch file for this? And I assume this fix is in the 4.14.3 update?