I am using Tiki Wiki, and I change to login with an LDAP server, I already made all the configurations but when I try to login with a user from my LDAP server give me a blank page. I saw a solution on TIKIWIKI doc's, they say to clear the cache but I dont know how to clear.
You can clear the Tiki caches by going to tiki-admin_system.php when logged in as an admin, there is a link on the Settings part of the main Tiki menu, and one on the Quick Admin module (if enabled).
You can also clear the cache from the command line by doing
php console.php cache:clear
More info here
(however, if you are running Tiki 16.2 there is a bug in LDAP which also produces this sort of blank page error. This will be fixed in 16.3 which will be released soon, in the mean time you can download a nightly build from here)
Related
I am starting the process of updating TYPO3 to higher versions (from the base 6.2.X version). The process of updating to version 7.6.X was ok. Being logged in 6.2 version, I switched to version 7.6 and updated elements in InstalTool, plugins etc. The problem appears when I log out. After entering my login address, I have a blank page - white page without any code. I can log into InstallTool but unfortunately not to BE.
The [FE] page works fine after the update. Any ideas what went wrong or where is the problem?
first: blank page normally means: there is an error but all error information was disabled.
If you just changed the source it might be a mismatch between cache and source: clear all caches in Install Tool.
Also your first step should be look into the server log.
If that does not give enough hints enable all debugging and error information in the Install Tool.
If that still gives no clue: disable all extensions (remove from PackageStates.php and don't forget to clear caches afterwards, maybe manually too)
I have installed the relatively fresh Visual Studio 2022 on a Windows installation. The work I do often requires administrative privileges (local IIS). To do this I have two users, one 'normal' account that is logged in to Windows and one administrator account. When starting VS2022 with the administrator account, an error keeps coming. It happens especially during debugging and it reads as follows:
Microsoft Edge can't read and write to its data directory:
C:\Users\<administrator_user>\AppData\Local\Temp\VSWebView2Cache\<guid>\EBWebView
What appears to happen is that Microsoft Edge WebView2 (msedgewebview2.exe) is running as the user that is logged in to Windows, while trying to write temporary files for the administrator user where it does not (and should not) have write or read access.
Here we can see the process details that says the application user is the logged in user and not the administrator:
Does anyone know how to fix this issue?
The error happen even when I run debugging on a .net 5 console application. In that particular situation I don't see why it needs to run anything in a WebView instance, but apparently some background process is running something anyway. Is this something that can be turned off?
My best solution so far is to create a shared folder.
I decided to make C:\Users\<administrator_user>\AppData\Local\Temp\VSWebView2Cache\ shared. The "VS" prefix indicates that this is a Visual Studio-specific folder, and I think it is acceptable that my normal user can have access to that folder as it seems to contain temporary Visual Studio files.
To do so I logged in to Windows with the administrator account.
I navigated to the folder and made it a shared folder. I added my no-admin user with "Read/Write" privileges.
I then tested by logging out of the admin account and into my no-admin account. There I first tried the full path in File Explorer and was granted access to the folder. I then tested with VS2022 and during debugging no error box appeared and files were generated in the folder.
If anyone finds a better approach, I'd really like to hear about it. Also if you have knowledge to why this approach is either good or bad, that would be highly appreciated as well.
I only had to create the folder "VSWebView2Cache" with my normal Windows account and after that it worked.
I was fixing things on a not well-maintained typo3 installation and it resulted in blank pages of frontend, backend and install tool.
I wanted to fix extensions because the powermail-extension was not working anymore even after updating to latest compatible version (tried emptying cache and database compare).
I deactivated an extension "compatibility6" to see if it was interfering and since then all pages have been blank including Install Manager. I reactivated the extension via PackageStates.php, emptied the cache but it did not change anything. I was not able to see any error messages even though I set the parameter in LocalConfiguration.php which made it hard to try to find out what is wrong. Then I restored a backup using vmware. Still, backend and frontend are blank.
I am using Apache and Typo3 7.6.23.
I do not know what might be causing the problem and would like to know what else to look for?
It means you have a PHP error there. The first thing would be to examine logs. If you see anything like "class not found", then your next action would be composer dumpautoload --no-dev.
Long time ago I had an article about blank pages in TYPO3 FE. Not up to date but still can be helpful: https://www.dmitry-dulepov.com/2009/03/blank-empty-page-in-typo3.html
Dmitry already wrote it: you have an error.
In production environment nothing is shown for not revealing any information about your system.
So the only information about the error can be found in the error log of your webserver.
What can you do to get more information about your error?
Enter the install tool and switch to develop mode. This will also enable deprecation logging into a file. Try to avoid filling your system with deprecation warnings by disabling deprecation logging.
Disable the default exceptionhandler by adding this to your typoscript setup:
config.contentObjectExceptionHandler = 0
Now you should see a call stack instead of blank screens.
Be aware that this might reveal confidential information from your system.
because of this you should use a copy of the live-system.
I tried to install without realising an older plugin than what was already installed. It errored with the install however now I cant get past the check plugins screen to fix my issue.
Reload just reloads the page, update does nothing. If I click Upgrade I get this:
I cant do anything else. If I try to reload Moodle with just http://moodle (Internal URL) I get redirected straight back to this page. If I clear my cookies I get taken to the login page, but after logging in it is straight back to the "Plugins Check" page again.
Do you have administrative access to the server running Moodle?
You should be able to download the version of the plugin you need and unzip it directly into Moodle's directory structure, and then log back in to the Web UI.
In my moodle installation, this is here:
/var/www/html/moodle/course/format/singleactivity
You should be able to get the correct files from the installation package you used. Just make a backup of the existing folder in your Moodle environment, move it to a safe location, and drop the complete folder for the new version in its place. Then reload the web client.
I'm working on setting up and migration of old sites to a new server from Dreamhost. I have 130 sites to migrate. 1 is successful. The version is: 1.12.1
The mods in the first site upgraded well. No problems. Have a procedure to migrate. That being said, the second site, as I followed my own documentation, fails when I try to access /admin/index.php
What I get is this below:
So, this is more informational than code... so please forgive me. I don't understand why CMS MADE SIMPLE is actually not simple.
That seems like an annoying issue. Forgive any repetition but here is what I would check:
that is is 100% functioning on existing server
correct php version 5.4.3+ (5.6+ recommended) on new server
that all files & database are copied fully & without errors
config.php settings are updated for new hosting & database
that .htaccess, php.ini/.user.ini settings are appropriate
check php error log
are there any additional modules installed that may require additional php modules
try more coffee or a nights sleep - both have helped me solve all sorts of issue in the past!
consider posting on CMSMS forum - will get a wider range of CMSMS users/experience and suggestions
Good luck
Chris
Not sure what process you are using. So presuming that the site was working correctly on existing hosting and that the new hosting meets recommended requirements, especially PHP version:
Export database
Zip/Compress all website files into a single file
Copy zipped file to new hosting
Create new database & user with full access
Unzip files and make sure that they are in the right location (probably website root)
CHMOD config.php to 0644 and edit database, username & password settings for new hosting, CHMOD back to 0444
Make sure .htaccess is using correct settings for new hosting
Login to admin and clear cache
Sorry that the instructions are so basic, but the process really is Simple.
Possible issues can occur if:
the PHP version is older than 5.4.3 (5.6+ recommended).
files copied individually using ftp and some are corrupted/not copied.
Apart from that it is pretty straight forward.
Hope it helps