FPA can't detect Joomla! and other critical info Topic is solved

This Forum board is about discussions about the FPA tool.

Moderator: General Support Moderators

Post Reply
User avatar
reggaebkk
Joomla! Enthusiast
Joomla! Enthusiast
Posts: 176
Joined: Mon Jul 14, 2008 1:39 pm

FPA can't detect Joomla! and other critical info

Post by reggaebkk » Thu Jul 13, 2023 3:40 am

Hi,
I think all should be setup properly with Joomla and FPA, but FPA seems unable to detect my CMS and other info such as DB version etc...
Is it a problem because I'm using PHP 8+?
Here is the return:
Forum Post Assistant (v1.6.6) : 13-Jul-2023 wrote:
Problem Description :: wrote:FPA can't find my website/server info
Log/Error Message :: wrote:No message, just missing info in most fields, no joomla version, no db version etc...
Log/Error Message :: wrote:No message, just missing info in most fields, no joomla version, no db version etc...
Actions Taken To Resolve wrote:I checked that all my website/server settings were following Joomla setup instructions... I can't find why fpa isn't working on my website, it used to be no problem.
Basic Environment :: wrote:Joomla! Instance :: Not Found
Joomla! Configured :: Not Found

Host Configuration :: OS: Linux | OS Version: 3.10.0-1160.53.1.vz7.185.3 | Technology: x86_64 | Web Server: Apache | Encoding: gzip, deflate, br | System TMP Writable: Yes | Free Disk Space : 43.56 GiB |

PHP Configuration :: Version: 8.0.29 | PHP API: cgi-fcgi | Session Path Writable: Yes | Display Errors: 1 | Error Reporting: 32759 | Log Errors To: error_log | Last Known Error: | Register Globals: | Magic Quotes: | Safe Mode: | Allow url fopen: 1 | Open Base: | Uploads: 1 | Max. Upload Size: 124M | Max. POST Size: 256M | Max. Input Time: 60 | Max. Execution Time: 30 | Memory Limit: 860M

Database Configuration :: Database Credentials incomplete or not available Nothing to display.
User Privileges : Unknown
Detailed Environment :: wrote:PHP Extensions :: Core (8.0.29) | date (8.0.29) | libxml (8.0.29) | openssl (8.0.29) | pcre (8.0.29) | zlib (8.0.29) | filter (8.0.29) | hash (8.0.29) | json (8.0.29) | pcntl (8.0.29) | readline (8.0.29) | Reflection (8.0.29) | SPL (8.0.29) | session (8.0.29) | standard (8.0.29) | cgi-fcgi (8.0.29) | bcmath (8.0.29) | bz2 (8.0.29) | calendar (8.0.29) | ctype (8.0.29) | curl (8.0.29) | dba (8.0.29) | dom (20031129) | enchant (8.0.29) | mbstring (8.0.29) | fileinfo (8.0.29) | ftp (8.0.29) | gd (8.0.29) | gettext (8.0.29) | gmp (8.0.29) | iconv (8.0.29) | imap (8.0.29) | intl (8.0.29) | ldap (8.0.29) | exif (8.0.29) | mysqlnd (mysqlnd 8.0.29) | odbc (8.0.29) | PDO (8.0.29) | pgsql (8.0.29) | Phar (8.0.29) | posix (8.0.29) | pspell (8.0.29) | shmop (8.0.29) | SimpleXML (8.0.29) | snmp (8.0.29) | soap (8.0.29) | sockets (8.0.29) | sqlite3 (8.0.29) | sysvmsg (8.0.29) | sysvsem (8.0.29) | sysvshm (8.0.29) | tidy (8.0.29) | tokenizer (8.0.29) | xml (8.0.29) | xmlwriter (8.0.29) | xsl (8.0.29) | zip (1.19.5) | mysqli (8.0.29) | pdo_mysql (8.0.29) | PDO_ODBC (8.0.29) | pdo_pgsql (8.0.29) | pdo_sqlite (8.0.29) | xmlreader (8.0.29) | Zend OPcache (8.0.29) | Zend Engine (4.0.29) |
Potential Missing Extensions :: mysql | mcrypt |
Disabled Functions :: show_source | system | shell_exec | passthru | exec | phpinfo | popen | proc_open |

Switch User Environment :: PHP CGI: Yes | Server SU: No | PHP SU: Yes | Potential Ownership Issues: Unknown

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 17445
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: FPA can't detect Joomla! and other critical info

Post by toivo » Thu Jul 13, 2023 4:06 am

reggaebkk wrote:
Thu Jul 13, 2023 3:40 am
Is it a problem because I'm using PHP 8+?
No.

Upload the FPA script into the main Joomla folder, the folder where the file configuration.php is stored and which has subfolders like administrator, api, cache and so on.
Toivo Talikka, Global Moderator

User avatar
toivo
Joomla! Master
Joomla! Master
Posts: 17445
Joined: Thu Feb 15, 2007 5:48 am
Location: Sydney, Australia

Re: FPA can't detect Joomla! and other critical info

Post by toivo » Thu Jul 13, 2023 6:03 am

You seem to have resolved the issue in the earlier topic, Error: Invalid Login when upgrading from 3.10.11 to 3.10.12.
Toivo Talikka, Global Moderator


Post Reply

Return to “Forum Post Assistant (FPA)”