Drupal 7. Clearing cache disables my administrative rights - caching

I don't know when or how this happened, but if I go to "admin/config/development/performance" and click on "clear all caches", I get the green notification that my cache has been cleared, but also a notice saying "You do not have any administrative items" and the page is completely empty now. If I now try to visit "admin/config" that page is also empty. I also loose my ability to edit any blocks on the page.
I'm still logged in though.
It doesn't matter if I log out and in again, or try to log in with another browser, or flush my caches, the site won't let me access these parts after a clear all caches has been made. I need to backup my database to get my rights back.
What could be the problem?

I found the problem. In my case, the folder 'ctools' within my plugins directory did not have the correct permissions set. It took a while to track down this problem since I was not getting any notices or warnings about this.

Related

Magento 2 problem redirect admin control panel

from one moment to another when I try to access the control panel, it redirects me to the following, apparently it is something about tickets or ticket system.
Has it happened to someone?
delete cache and the problem continues, also go from developer to production mode and vice versa but no apparent errors are seen

Access 2013 Update Query blocked by Disabled Mode

I am attempting to run an update query and receiving an error in the status bar "The action or event has been blocked by Disabled Mode".
EVERYONE IS RECOMMENDING THIS ARTICLE. The action or event has been blocked by Disabled Mode
PLEASE READ THE BULLET POINTS BELOW. That article does NOT fix the issue
1) I have no messages asking to enable or anything like that.
2) I have checked and there is nothing labeled security warnings or anything like that on the External Data tab
3) I have checked the Access Option for Trust Center Settings "Show Message Bar" is checked.
4) I have googled anything else I can find. There was a reference to Database Tools tab, but there should be some "Show/Hide" section that doesn't exist and
I can't seem to find what they're asking about. Any help would be so appreciated.
Though I was working with the tech guys at my work and they were saying that it's not a trusted location.
I answered my own question. I'm on a work computer, it's managed (naturally). So there is an un-editable list under Trusted Locations. When I moved my DB to one of those locations, all started working fine.
Hope this helps other people.

TYPO3: Issue with the install tool in 7.6.9

I've installed the TYPO3 from scratch on an empty DB.
Everything worked fine until I reached the point where you have to create your first Backend user.
Well, I filled in the form and clicked "continue". Then, the page reloaded and nothing happened. Checking the DB showed me that the Backend user has been created, so I left the Install Tool and accessed the Backend via "domain.com/typo3". Logging in worked fine, as well.
But now, when I try to access the Install Tool in the BE (via the tab on the sidebar), it still wants me to create my first BE user. The installation process stays permanently on 80%.
I'm looking for a method to trick T3 to think that the installation process is finished, because it actually is.
The only thing I did differently than usually was to click on "Continue, I know what I'm doing" in the first step. T3 complained about the always_populate_raw_post_data=-1 and I created a php.ini in the root directory to fix that and continued without checking because I thought it'd fix the problem.
Thanks!
You can check this setting in your LocalConfiguration.php:
$GLOBALS['TYPO3_CONF_VARS']['SYS']['isInitialInstallationInProgress']
You have to set it to false.

CodeIgniter Blank Page

n00b here. After searching the forums I have not yet come across this problem as I am experiencing it.
I have a CI site that was working correctly until about three days ago. My problem is as follows:
On button click - Page Loads correctly.
On Enter press - CI Blank Page of Death loads.
For example: When I login, after the login process has run it must reroute me to the Dashboard, unless I still have a temporary password where I get rerouted to the "Change Password" screen first and then to the Dashboard.
AS LONG AS I USE THE BUTTONS AND CLICK THEM EVERYTHING WORKS.
On ENTER PRESS, I get the Blank Screen of Death.
However, on TAB to BUTTON and then ENTER it works.
The problem is not consistent however. I have some processes that do not have views attached and NONE of them will run - hit ENTER and get blank. They are all failing on ENTER PRESS.
I am slowly going off my trolley. Logging is ON, Directories for cache and logs are 775. NOTHING is showing in my logs...
First Try to active error handlers for displaying of errors for addittional info to post here what error is occuring..
// change settings for error handler to show errors
// $this setup is used for checking errors for development to be shown....
ini_set('display_errors', 1);
error_reporting(E_ALL);
by the way if your using CI version 2 higher
you can see it in its index.php file an configuration for displaying error also.
define('ENVIRONMENT', 'development'); //just set up environtment to development
Even though there are accepted answers I wanted to add a way that worked for me to figure out this problem.
Usually the "Blank Page" indicates a PHP parsing error somewhere in the code. Strange thing for me was that on my local MAMP based test server the code ran fine. I FTP it to my hosted server and all of a sudden, blank page of death.
Even though I had errors on, log errors on, display errors on, nothing appears in any log file.
I was able to find the error by a funny little trick. I added an echo line in CodeIgniter.php in the system/core. Obviously hacking the core was not a great idea but all I wanted to do was to see how far it was getting in the load process.
When my echo appeared after trying to load a page on the remote hosted server it also displayed the parsing problem in a derived controller! Not sure why the error did not come out without the "echo" added. But adding it seemed to trigger some output to be generated, IE my echo line and the PHP parse error was appended.
Not sure if this will help anyone but it turned out to be a nice easy way to find the error which only showed on the remote server.
Obviously, don't forget to put your core file back to its original state without the echo.
This was fixed by copying the application into a fresh CI 2.3 install.
I have no idea what actually caused this "erratic" behaviour.
The application worked correctly as designed whenever a BUTTON was CLICKED but gave the blank death screen when ENTER was PRESSED.
This inconsistent behaviour is what threw me. The fact that my logs (CI and APACHE) also showed nothing was also very strange. Had this been a parse error, surely the behaviour on "Click" and on "Enter Press" should have been the same.
My non-view controllers for various ad-hoc admin jobs are now also working correctly, which they were not before, as they use "Enter Press" (having no buttons to "Click").
I am still going to invite best guesses as to why this behaviour occurred the way it did.
Surely someone out there (Phil Sturgeon et al) with extensive CI experience has encountered this non-consistent blank screen behaviour and knows what caused it.
Thank you to all the people who took the time and effort to assist me!!!
Big UP!!! StackOverflow!!!
probably error in INCLUDE login.php
My problem was Apache stop working because of ...Skype! Skype actually work on the same 443 and Apache didn't start! I hate this Skype! Bring me nuts for a while.
Installing php5-pgsql worked for me

How to produce a XHR log silently with Chrome

I would like to spot a "random" bug on a site. In order to do that I would like to have all the XHR requests saved in a log file, which is a very easy thing. The problem is that I'm not the user, so I have to set up someone else's machine to do that.
The problem is that the user doesn't know how to use the "developer tools" so I would like to have a tools that keep trace of everything without bothering the user. Bear in mind that this bug can occur once in a day and during this time the user can close the browser and re-open it. Do you have any suggestion? thanks!
I think that the best way would be to make the logs from within the site that you're trying to observe.
If you don't have access to it, another solution might be to find/develop a browser extension that logs any xhr to a local file.

Resources