Oracle APEX Error : Page Protection Viiolation - oracle

Page protection violation: This may be caused by submitting a page that had not yet finished loading or by manual alteration of protected page items. For further assistance, please contact the application administrator.
Getting this error in Oracle APEX Version 20.2
Please let me know if anyone can help on this one.

Usually, there's a hidden item on a page whose Value protected property is turned ON. So, turn it OFF (or don't manually alter its value).

Related

How to add Logout in oracle apex 5.0

I'm a student with virtually no oracle apex experience, I created a custom authentication for my login system.
However I have no idea how to log a user out, Everything I have tried has resulted in a multitude of various errors.
Would appreciate any help.
Go to Shared Component -> Navigation Bar List
Select the active list
Create List Entry
Place &LOGOUT_URL.in URL Target
Refresh your page and you should able to see the Log Out button on top of the page

Mangage Customer edit display blank in magento admin panel

We have Added this code
"ini_set('display_errors',1);"
in index.php but there is no error.
Please tell me another solution. Is any problem in Database or server issue?
Try to enable developer mode from index.php
And check what is error display.
Please check the logs if you get some clue there.
Also, have you used any extension which is overriding the Customer management in admin. If yes, you can try to disable it once to identify the issue.
I hope you have ensured that its happening with the edit page and not for a particular customer.

Magento Products display not displaying products in backend on reindex

I am running Magento 1.8.1 with embeddedERP extension.
Not sure if extension is to blame for the behaviour, i don't think so as it seemed to work fine for a while after I installed the extension. The issue appears to relate to indexing.
I reindexed the site in response to a magento index aler. When I try to view products in the backend the page is blank but only from from the horizontal line below the Add New product button, there is no list of products but also no products table at all, rather than the products table with no rows one would expect.
I have tried deleting cache and session folders.
I've tried disabling cache.
I enabled logging and there isn't an exceptions.log file so presuming this means no exceptions happening.
I've logged in and out.
On one occasion when i tried creating a new product after saving it it displayed the products (new one and existing) but now that doesn't work either.
Previously, deleting session and cache and logging back in appeared to work but now doesn't.
Can anyone suggest how I can go about working out what is wrong. My magento debugging skills probably need some enhancing.
Thanks,
Came back to this and the site was then displaying an error:
Warning: Unknown: Unable to allocate memory for pool in [filepath]/Autoload.php
This thread:
http://www.magentocommerce.com/boards%20/viewthread/216180/#t462005
highlighted this is as an apc issue.
Altering the memory size to 256M as suggested solved this.
Hope this helps if anyone else gets this, still don't know why this issue showed a blank screen to start with, perhaps an APC caching issue?

Session issue in codeigniter for arabic character

I am just stuck with a issue regarding session. I have a multilingual ecommerce site for english and arabic language. In case of arabic language when someone registers with a arabic name, description or such fields s/he can register successfully. But during login the session data being lost.
Actually when setting all the data into a session array its being stored and i tested it by printing the array. But after the valid authentication when user being redirected to index page or profile page then the session array disappears. The full array being lost. and login doesnt working. Its only happening for someone who has arabic fields on their data. for english its perfectly ok.
I have removed the session.php from syatem/libraries directory. Then it works only on localhost, on server it creates problem when ordering or viewing items of a particular org.
Any suggestion will be accepted cordially.
Thanks
Thank u so much all of u for your reply.... and my issue has been solved.
Unfortunately my session table user_data field collation was not utf8_unicode. Thats why the data was being lost when it redirects to home page. Since it is using the ci_session table. Its working now nicely.
Before posting the question i have tried using native session, updated the Session.php file on system/libraries....But haven't got the perfect solution.
But finally could have figured out the silly mistake and done with the issue.
Cheers to all....:D
Thanks
Please try to use Native Session instead of default CI_Session and see if your problem will be solved?
Here is a link for you:
https://github.com/appleboy/CodeIgniter-Native-Session

Cannot log in or add items to cart in Magento after migrating to new server

I have migrated a Magento site to another server (the same server the database was already hosted on) and I am no longer able to log in or add items to my cart. I have found a few others who have posted about this type of problem but nothing seems to work for me. I have disabled all caching, etc. Ensured that sessions work. Increased the session lifetime. No errors are being logged anywhere. If I enter wrong credentials I get an error. But if I enter the correct information it just keeps returning me to the login page. I have opened permissions completely. Nothing makes any difference! So aggravated. Please help!
Found the issue. Well sort of. I think there was a problem with the timezone (the server I moved to was an hour different from the other) but essentially I resolved the problem by increasing the values for two config items in core_config_data:
UPDATE core_config_data SET value=86400 WHERE path='web/cookie/cookie_lifetime';
UPDATE core_config_data SET value=86400 WHERE path='admin/security/session_cookie_lifetime';
The first query fixed the shopping cart problem, the second the admin login problem.
Again I think there is a mitigating factor here as well, but this at least got me over the hump.

Resources