update build 3381_4096

[dalebra]

Re: update build 3381_4096

Hi Dale, Keith

I think I will wait for a couple of days as well, as I haven't seen any feedback yet.

Thanks for the info

Robert

I see this wait and see game paying off for me!

[webcommerce]

Re: update build 3381_4096

Hmmmm .... I've been reading all this and rather nervous about updating from build 3044. I have an issue with the Submit button (set to "Save Submitted Data to Tables", which I am informed is corrected with the new release. Being new to all this, I'm reluctant to proceed if there is an earlier rebuild that is proven and also corrects the problem I have. Can anyone tell me if this is so??

Also, in the Release notes this important note:

VERY IMPORTANT: Before using this upgrade you must publish as least one page or component to your server (does not matter which one). This will cause a new version of the __a5RunGrid.a5w and __a5RunReport.a5w system pages to get published. If you do not publish at least one file, your app will still be using an old version of these system file and it will fail. (You do not need to republish your entire application).

What does this mean? Does it apply to Local host and external server, one / other / both? As I said - Nervous!!

Ron S

[frankbicknell]

Re: update build 3381_4096

Anyone else have this? Customer came to me today, said he updated to this build, and is getting 403 permission denied errors all over the place. I narrowed it down with him, and found it happens when control is dirtied. With some further testing, I found that if I turn off the component security, the problem does not appear. Before turning off component security altogether I just tried setting one of the components (for a test) to Always Allowed, but that didn't do any good. Instead I had to completely turn off component security in the Web Security Configuration.

I can dig further, but this appears to be the culprit and wanted to check to see if anyone can confirm.

I have component security enabled and have updated to build 3381_4096. The only issue I have is that it seems like I have to save one of my grids a couple of times after editing before the changes show up after publishing. It may be a cache issue though.

[Progytech]

Re: update build 3381_4096

After a careful review of my grid "StudentsSessionsGrid" security, I noticed the following:

1. The security for the grid, did not include the group of the users which are mostly logged into the system.
2. The grid was being shown linked to another grid and in the linked security did not included any security groups, so now I defined the security groups the same as the grid itself.

I am currently waiting for users to log off so I can update the system and see if this error goes away. The weird thing is that I never got this error with previous version, so go figure

Will post results after update and seeing some log entries tomorrow morning, well, actually in a couple of hours

[kingcarol]

Re: update build 3381_4096

Update on my progressive edit combo bug above. Alpha says that this has now been fixed.

[Progytech]

Re: update build 3381_4096

Hi Steve,

Anyone else have this? Customer came to me today, said he updated to this build, and is getting 403 permission denied errors all over the place...

Today I started getting this 403 error on a Row expander linked control. Security for any of these control has not changed, so this must definitely be something else, I will submit a bug report..

[Peter.Greulich]

Re: update build 3381_4096

Me too. I had to go back to 3044- 4041.

[agillbb]

Re: update build 3381_4096

I've been live on 3226-4073 since early February without any problems.

[Progytech]

Re: update build 3381_4096

Hi All,

The fix to the 403 permission error is pretty simple. I got a fast response from A5 support and here is the quote for this fix:

The problem is caused by having the Component Security enabled, but the option to always enforce security at the component level is not checked.

We recommend that Always enforce security at the component level is also selected. If you activate the option, the problem should go away

See image attached.

[Peter.Greulich]

Re: update build 3381_4096

Unfortunately for me, I already had security with those options selected. Something else is going on.

[Progytech]

Re: update build 3381_4096

Peter,
If you tried again and published all files and those options are checked, then I would suggest you open a bug report and be sure to include all the server logs, specially the http raw log and the Pages.SecuritySettings file which should be in your server's root folder.

[Peter.Greulich]

Re: update build 3381_4096

Edhy,

These option have always been enabled. But yes, when I have time i will do that.
Thanks

[Kamel]

Re: update build 3381_4096

hi,,,
First there is an issue with internet explorer 8 in grid search, that submit the form as GET and no result :S
And in other browsers u can't select text in the page ?!?!?

[Peter.Greulich]

Re: update build 3381_4096

Me too. I had to go back to 3044- 4041.

Oops! I totally screwed up yesterday when updating the patch. It's all working fine now. I updated to today's patch which is labeled Build 3393-4098 26-Mar-2103 9:28 AM, but in reality is 3396-4099 - or at least that's what it was an hour or two ago.

[iviowa]

Re: update build 3381_4096

I'm also getting the 403 Security Error after doing the single page published per the service pack release notes. The release notes say the reason for the publish it to get the update files "__a5RunGrid.a5w" and "__a5RunReport.a5w" on the server. I restored my website files to their status before the single page publish then just copied the two .a5w files to the server. I no longer get the 403 errors and my brief testing looks good. I don't know if this approach is recommended but thought it might be helpful information.