The Attribute Manager that Logs you out!

[jack_strit]

HI,

So if we have a contest to see who can come up with the weirdest errors, who wins?

Well, I am going to submit my most recent error to the contest:

Per the suggestion of the powers that be I tried to fix a bug in rc3 in the attribute manager.
****
Yes that is fixed in RC4, and you can also get the fix for RC3 in the bugtracker:
183: RC3 Attributes Manager Issue - no attributes aren't selected. - Bug Tracker - open source Commerce Maximized :: osCMax

******

The suggestion was that we needed a couple of = signs in there....

Tried it last night according to the Bug Tracker...wala..a blank page.

Next, I went over to the RC4 repository and snagged the code for the pages new_attributes_select.php and new_attributes_include.php and replaced the code of each page. Now, when I go to attributes manager there is the little dropdown with the products in it...and when I select one and click edit it takes me to the admin login page!!! Ok, that is really crazy, probably not the craziest error ever, but maybe I would get a close 3rd place!

Anybody with a suggestion?

J

[michael_s]

1st suggestion: don't use bits and pieces of RC4 in your RC3 shop. Either use all the RC4 code, or none of it. There are too many changes to go piecemeal, and you will get unexpected results like being logged out for no apparent reason. Mixing development code with released code is usually never a good idea for a soon-to-be live store.

2nd Suggestion: Revert to the rc3 default files and re-apply the patch in the bugtracker. This time, when you get a blank page, check the server error logs. That blank page means you have a syntax error in your php somewhere and the error logs will tell you exactly where.

Then post that error message here and we will help you resolve it.

[jack_strit]

HI, I found the answer last night late.
file:admin/new_attributes_includes.php
The original code was this (on lines 5,6,7):
<FORM ACTION="<?php $PHP_SELF?>" METHOD="POST" NAME="SUBMIT_ATTRIBUTES">
<INPUT TYPE="HIDDEN" NAME="current_product_id" VALUE="<?php $current_product_id?>">
<INPUT TYPE="HIDDEN" NAME="action" VALUE="change">

The suggested fix according to the bug tracker was this:
<FORM ACTION="<?=$PHP_SELF?>" METHOD="POST" NAME="SUBMIT_ATTRIBUTES">
<INPUT TYPE="HIDDEN" NAME="current_product_id" VALUE="<?=$current_product_id?>">
<INPUT TYPE="HIDDEN" NAME="action" VALUE="change">

The solution that worked for me:
<FORM ACTION="<? $PHP_SELF?>" METHOD="POST" NAME="SUBMIT_ATTRIBUTES">
<INPUT TYPE="HIDDEN" NAME="current_product_id" VALUE="<?=$current_product_id?>">
<INPUT TYPE="HIDDEN" NAME="action" VALUE="change">

I really am not sure why it worked for me this way, but it did. Anyone have an explanation?

J