Jump to content

UniSite CMS v4.11 NULLED

Featured Replies

  • Replies 62
  • Views 13.6k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

Most Helpful Posts

  • Монатик No23
    Монатик No23

    FilesMatch "config\.php"> Require all denied </FilesMatch> <FilesMatch ".(htaccess|temp|sql)$"> Require all denied </FilesMatch> RewriteCond %{REQUEST_URI} !/login.php 1. Outdated

Posted Images

4 hours ago, Razvan Serban said:

Hello, I can't log in to the admin panel. Do you have any idea why? This is what my admin page looks like.

1706895831889.thumb.jpg.87e86bb6bd5647cfc3911a9e0a0632f0.jpg

Listen check to config file and put correctly the link path of your website, and path admin correct, ive done like this and work fine for me.

установил 4.11 вся работает кроме VİP i Turbo объявления не показыается на главной странице ктото сможет помочь 
installed 4.11 everything works except VIP and Turbo ads are not shown on the main page can anyone help

Edited by Aytac Bayramzade

Hi,

Users cannot create an account because sending the code does not work, nothing arrives in the email box

code-2024-07-04-a[...jpg

FilesMatch "config\.php"> Require all denied </FilesMatch> <FilesMatch ".(htaccess|temp|sql)$"> Require all denied </FilesMatch>

RewriteCond %{REQUEST_URI} !/login.php

1. Outdated Order directive syntax

The Order directive is deprecated, and Apache 2.4 no longer supports it. If you're using Apache 2.4 or a newer version, you should use the Require directive instead of Order.

Your <FilesMatch> configuration should be updated like this:

apache

Kopēt kodu

<FilesMatch "config\.php"> Require all denied </FilesMatch> <FilesMatch ".(htaccess|temp|sql)$"> Require all denied </FilesMatch>

2. PHP settings (mod_php5)

If your server is running PHP 7 or newer, mod_php5.c is no longer supported. You should use the appropriate mod_php module based on your PHP version. If your server uses PHP-FPM, these directives won't work. You need to check whether your server is configured with the correct PHP version and settings.

If you're using a newer PHP version, this part of the configuration might need to be removed or adjusted, as certain settings (e.g., magic_quotes_gpc) are deprecated.

3. RewriteRule and URL request configuration

The RewriteCond and RewriteRule directives seem correct, but if the login page isn't working, there might be an issue with URL redirection. Ensure that the URLs are correctly passed to index.php and that the .htaccess file uses the correct paths.

If the server is misconfigured, the rewrite rules could prevent login or other parts of the website from loading.

Check that index.php handles the requests properly.

4. Protection via .htaccess

Ensure that login scripts are not directly blocked by .htaccess, as this could cause issues with logging in if access is being blocked unintentionally.

Example of adjusting RewriteRule: If using index.php causes issues with the login process, you may need to add an exception for the login page:

apache

Kopēt kodu

RewriteCond %{REQUEST_URI} !/login.php

5. Check server logs

If the problem persists, check the server logs (e.g., error.log and access.log) for more information about errors. Server logs can provide hints about what is happening and why the login isn't functioning properly.

6. Check PHP errors and session settings

Ensure that PHP session handling and error reporting are configured correctly. Any errors related to session handling or data processing during the login could result in login failures.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

Recently Browsing 0

  • No registered users viewing this page.

Latest Updated Files