I tried to upgrade Magento to 1.8. on my localhost version.
The front-end works well, but my admin is completely empty. No error messages, nothing.
I removed the sessions, the cache and commented out the cookieparams with no result.
Where do i have to look?
Thnx!
Check magento_site/var/log/exception.log and magento_site/var/log/system.log files.
If (1) didn't help, turn on error reporting in php.ini. Set $_SERVER['MAGE_IS_DEVELOPER_MODE'] variable so something not-empty (true is OK). Reload page.
Related
After upgrading from django 3 to django 4, the "Sign in with Apple" feature started breaking with the following error
Your request could not be completed because of an error. Please try again later.
The javascript, the frontend html, and the Apple ID url are all identical, and there is no useful error in the console. What is going on?
So it turns out that Django 4 added a new setting called SECURE_CROSS_ORIGIN_OPENER_POLICY which sets the Cross-Origin-Opener-Policy header to same-origin.
Adding the following line to my django settings module resolved the issue for me
SECURE_CROSS_ORIGIN_OPENER_POLICY = "same-origin-allow-popups"
I am not sure why they did this because the default browser value is unsafe-none, and the browser error console was not very helpful.
I've got django-debug-toolbar 1.9.1 working fine in my configuration (Django 2.1.2), but if I simply update it to 1.10 or 1.10.1, without changing anything else, it doesn't show up anymore. I don't see anything in the change logs that indicate I need to update any settings.
Does anyone have any suggestions? Or there a way I can turn on some kind of logging to see where it's not working?
Thanks!
This issue on GitHub was solved by refreshing the browser cache.
Try running manage.py collectstatic and refresh your browser cache, to make sure you aren't running javascript from an old version.
I had this issue when running 'manage.py runserver'. All I had to do is Refresh my browser cache. In Chrome, you just open View/Developer/Developer Tools and now right click the "Refresh" button and click 'Empty Cache and Hard Reload'.
That did it for me (using Chrome), same thing under Chromium. Cheers!
I'm having a problem where Django's login is working okay on Chrome but not on Firefox: when trying to login to a restricted portion of the site on Firefox, it simply loops back again and again to the login page; furthermore, no error message appears on the log regarding that.
Interestingly, the error doesn't happen when the server is on the local machine.
Does someone have a general idea of what could be causing that strange behavior?
I'm using Django 1.6 on Python 2.7
this isn't much of an answer, but a linking to other similar problems. Because I don't have rep, all I can do is leave an answer.
A issue like this was encountered in 2012 but was never conclusively answered:
Django session doesn't work in Firefox
A similar question where the user could login via local server but not remote firefox was encoutered:
Unable log in to the django admin page with a valid username and password
The second was very well documented and had an accepted answer that was well liked.
Recommendations:
If you are not using https make sure you have this setting SESSION_COOKIE_SECURE = False.
If you are using a database backed, Check if the session is actually being created in the django_sessions table .
If you are using a cached backed, check that SESSION_ENGINE is django.contrib.sessions.backends.cache and that CACHE_BACKEND is properly configured.
Web site functioned normally , I tried to login to admin page and suddenly when I access admin page it display:
404 - An error has occurred.
Component not found
No new extension/module/component and theme has been installed.
No changes on PHP or mysql on the server side. ( I did check with hosting providers).
It's like it works today and tomorrow when you want to login , you'll see the above mentioned error.
Renaming .htaccess did not solve the issue.
Restoring DB backup did not solve the issue.
I checked the Joomla logs ( in log folder) there isn't any related report.
Joomla version info:
$RELEASE = '2.5';
$DEV_LEVEL = '16';
Please help!
I managed to sloved this long time ago but I forgot to update!
It is solved by running repair and optimize operations on the database via phpmyadmin.
This is starting bug me: whenever I use the django admin to add or edit a record, I hit save and expect a confirmation page, but the result is a page that tells me the website is experiencing an error (it's not a Django page with a traceback, just a default view in my browser). If I hit reload or back in the browser, it takes me back to the user form. Even though the confimation page doesn't display, it never fails to save my entry in the database, so it's apparently just a problem generating/serving the confirmation page.
Has anyone else had this problem? Am I missing something obvious?
My server: Django dev server
My browser: Internet Explorer 7 (but same problem occurs with any broswer I use)
My OS: Windows XP
I got such a behaiviour when I overwrote __init__ incorrectly. Or to be more precise when switching to a new version of Django with these worng __init__s. That was the day I started to love signals :D.
Can you post your models?
This is certainly not how it's supposed to work! Have you been messing around in the Django codebase at all? The first thing that comes to mind here is a "pdb.set_trace()" left by mistake somewhere in the change_list codepath. Off-hand I can't think what else would cause the server to simply not respond.