Support

Admin Tools

#13503 unpack jpa

Posted in ‘Admin Tools for Joomla! 4 & 5’
This is a public ticket

Everybody will be able to see its contents. Do not include usernames, passwords or any other sensitive information.

Environment Information

Joomla! version
n/a
PHP version
n/a
Admin Tools version
n/a

Latest post by nicholas on Tuesday, 11 September 2012 15:07 CDT

user43592
Is there a simple way to unpack .jpa without taking it through the akeeba system? For example if there are certain files I want from it.

Perhaps Google would have the answer. I just clicked "new" by accident and wrote "unpack jpa" thinking I was searching through other tickets.

I also see i am in the admin tools category.
The reason being i have admin tools running on a joomla 1.5 installation..


everything worked fine until i decided to try the .htaccess creator for enhanced security. that created a blank screen.

the blank screen did not go away even tho i deleted .htaccess and replaced it with htaccess.txt, giving the needed permissions as well as restarting varnish and apache. no luck.

i thought maybe theres a modication done to the old .htaccess that i have saved in an older .jpa backup done with akeeba, due to varnish cache. hoping that will fix the problem.

nicholas
Akeeba Staff
Manager
You can extract the archive locally using Akeeba eXtract Wizard. Then you can take the one file (.htaccess) you want. There is no way to extract only one file from a JPA archive.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user43592
well, this is a problem.
i took the old .htaccess and still i get a blank page.

i chowned the right permissions for the .htaccess of course, restarted apache and varnish, but nothing. the blank page is not going away. and this is only for the frontend side of the site.

backend access works fine (and has been working fine the entire time). no blank page there. or when i close the site and set the Site Offline to yes, it works fine - no blank page there.

the blank page is only on the frontend. any ideas?

nicholas
Akeeba Staff
Manager
A white page or a page with a 500 Internal Server Error is, in fact, either a .htaccess issue to a PHP fatal error in disguise.

I guess we're past the .htaccess checking already.

So, the error you are receiving is in fact a PHP error in disguise. First, check your server's error logs (not the access logs) immediately after visiting the page which throws the error. There should be an exact description of the PHP fatal error which occurred. Sometimes you can find the error messages in files called error_log or error.log inside the site's root and/or administrator directories. If unsure about the error log location, please consult your host. Most likely the error logs are available in your site's cPanel, Plesk control panel or similar hosting account management facility.

If your host does not give you access to the error logs and you have access to the Joomla! administrator area, please log in to your site's back-end, go to Global Configuration, click on the Server tab and set the Error Reporting to Maximum (Joomla! 1.5) or Development (Joomla! 2.x and later). Try visiting the problem page again.

If you still get a blank page, edit your configuration.php file and put the following code right after the final closing curly brace ( this is what a curly brace looks like --> } ) but before the closing PHP tag (it looks like ?> that is a question mark and a greater-than sign):
ini_set( 'display_errors', true );
error_reporting( E_ALL ); 
Try visiting the problem page again.

If you still get a white page, please remote the two lines from your configuration.php file. Edit the .htaccess file in your site's root. If you don't have a file named .htaccess create a new one. Beware that htaccess.txt is a DIFFERENT FILE and will NOT work! Add the following to the end of the file:
php_flag display_errors On
php_value error_reporting 32767
and retry loading the problem page.

If you still get a white page, remove the two lines from your .htaccess file. Now, create a file called php.ini with the following content:
display_errors=on
error_reporting=E_ALL
and upload it into your site's root and your site's administrator directory. Retry loading the problem page.

If you still get a white page, delete the php.ini files your created and, dunno, maybe choose a different host? If your host doesn't allow you to debug any PHP-related issues you're just stuck between a rock and a hard place.

Please note that if you can not understand what the PHP error message means, just copy and paste it here verbatim so that we can take a look and point you to the right direction.

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

user43592
thanks man. everything works now. of course i shouldve checked that to begin with, but turns out (from tailing error.log) that a module for joomlawatch (which i uninstalled earlier today) was the cause of the blank page, NOT admin tools.

admin tools .htaccess setup now works with every feature enabled. :)


thanks again.

nicholas
Akeeba Staff
Manager
The obvious stuff is the hardest to spot. Speaking from experience :) I'm glad it's all working now!

Nicholas K. Dionysopoulos

Lead Developer and Director

🇬🇷Greek: native 🇬🇧English: excellent 🇫🇷French: basic • 🕐 My time zone is Europe / Athens
Please keep in mind my timezone and cultural differences when reading my replies. Thank you!

Support Information

Working hours: We are open Monday to Friday, 9am to 7pm Cyprus timezone (EET / EEST). Support is provided by the same developers writing the software, all of which live in Europe. You can still file tickets outside of our working hours, but we cannot respond to them until we're back at the office.

Support policy: We would like to kindly inform you that when using our support you have already agreed to the Support Policy which is part of our Terms of Service. Thank you for your understanding and for helping us help you!