We have a simple SQL Server database with an ASP.NET front end.
I can easily update a record from my browser.
Another person cannot: he edits the field and hits the "update" button, but the change is not propagated to the database. The old value remains. He is using Internet Explorer. I checked the database, and his change is not propagated. There is no error thrown.
He WAS able to edit in May. Today he can't. but I can.
I can even update it with the Google Chrome browser.
Any ideas why his browser can't update, but I can?
Thanks!
Check thoroughly your stored procedures and application structure, it might not be a browser issue at all. There must be some permission or user level problem in application.
Related
I have a running Kentico 11 portal engine site and need to update the transformations in my navigation menu control. Something I have done many times before.
Today I went through all of the steps and the save button does not update the code. It never displays the change were saved messaging.
When I open the browser dev tools I see several errors on the page:
errors
A couple of things to check.
Is this happening in different browsers, also?
Can you save other transformations?
On this particular web part, if you select a different transformation, will that save successfully?
And, is the event log registering any errors?
Sounds like it may be a caching issue. What I'd suggest is the following:
restarting IIS
Open a private browser window and log in
attempt to make an edit to the code in question
If this does not resolve the issue, have you made any changes recently to the web.config, in particular the CMSHashstringsalt value? If so, this will cause your macros to become invalidated. You'll need to go to System > Macros > Signatures and check both boxes and resign the macros. It may take some time depending on your site but this could also help resolve your issue.
I just created a firebase project. And the database in the console appears empty. On previous projects, when you clicked on the empty white area, you were able to create database items by hand.
But clicking it doesn't do anything.
The rules tab is loading indefinitely, and i can't type anything.
I'm on Chrome last version, do you encounter such problems by creating new projects?
Here are some screenshots:
Ok, quick answer to my own question as i wasn't able, from my Angular2 App, to interact with database as well via websocket.
I'm working in a company with a (strong) proxy setup file. Disabled it on windows settings and all works now perfectly. Firebase website appears to rely on websockets.
Hope this information can be useful to someone else!
Currently facing some interesting behaviour of update preview functionality with XPM.
Post adding components to page XPM service/oData service pushed the data to db n respond back session based filter response.
Updated content is available at page source however update preview is not reflecting changes on page.
Looking for pointers to resolved thus issue.
We are using only one staging website which is enabled with XPM.
Session preview is in place.
Just thought, may be silly, same page getting edited with same credentials from different browser session break update preview?(Two or more Session Preview ID is getting created for same user is trying to edit the page from different machine (laptops) hence we are facing inconsistent behavior and session is getting locked e.t.)
Thanks ! Hiren Mistry
I having a problem using vTiger.
Actually i had no problems but we had to format one of our servers and as the SQL has been backup'ed i had no worries about vTiger.
Just got vTiger folder backup'ed too, but when i had my server back and put the folder of vTiger into www and restored the database i had a few errors, mostly resolved by re-configuring config.inc.php because paths had changes. But after all the configuration is done again i can't login to my vTiger. He reachs the database but does not recognize any of the users. I alway get username or password is wrong. Have anyone experienced this? Is there any possible solution?
Had a similar problem a few days ago, it turns out my cookies were corrupt (Firefox). I cleared all related cookies, problem solved. Try first using some other browser to confirm. hth.
First I would check if the db is reached and populated with your data. Try connecting from the command line.
If you are working on Windows and have changed Vtiger's path, and you are using the bundled version, MySql path changes as well, but the Windows service can still be alive on the old path: in this case you must manually cancel the service and afterwards use the "Start Vtiger" button in order to create the new service.
Second, I would turn on the php debugging as explained here. In most cases, these steps should help you.
Have you checked user_privileges folder? in that you must have 2 files for particular user. eg. your user admin having id 1 in database then you must have user_privileges/sharing_privileges_1.php and user_privileges/user_privileges_1.php file
and open user_privileges_1.php file and check username/password in that file, if it's not same with your DB then change it manually.
Try this solution and let me know if it works.
I have got a web app working in Safari 5 on the desktop that writes to a local storage database - not problems! Able to add, update and delete records fine.
I then set the web app up on the iphone, but it seems to be ignoring all database transcattions except creating and dropping tables.
It does not matter whether the app is on line or off line. If I add a record, it does not get added to the database. I enabled the debug console, but there are no error messages.
The instruction to add the record just seems to be ignored! It doesn't matter which page of the app i am on and I have made sure that only the index file has a link to the manifest...
Suggestions would be very welcome!!
Dave
OK... Thanks if you looked at this...
:)
Turns out that when the app was locally cached, the page refreshes were happening too quickly for the data to be added to the database!
I have added some settimeout's and all is peachy...
Sorry to anyone who went for it...
:)