• Installed Akeeba Backup CORE for WP V1.0.b4 and it did not work for me.

    Activated it, clicked on Akeeba Backup in the sidebar per installation instructions.

    A blank page is displayed and there is no configuration button to start the backup process.

    Logged into my WP dashboard on IE 11 and FF 29.0.1 just in case it was a browser issue, still did not work.

    Theme: Customized WP theme.

Viewing 14 replies - 1 through 14 (of 14 total)
  • Plugin Author nikosdion

    (@nikosdion)

    We have just released version 1.0.0 (stable) which fixes this issue. Please make sure that your server does run PHP 5.3.4 or later. Earlier versions, while supported by WordPress itself, are not compatible with our software.

    If you have found a bug please report it to us through the Contact Us page on our site. If it’s a legitimate bug we will investigate it and provide a prompt fix.

    Usually this is an indication that you should reinstall the plugin. This plugin definitely works.

    Plugin Author nikosdion

    (@nikosdion)

    We’ve actually found a situation which explains why this issue might occur.

    Since WordPress does not have its own session management (well, not without committing data data to the database) we implement our own solution using session cookies. The problem is that the name of the cookie is always the same. This means that if you have multiple sites on subdomains of the same domain name (e.g. blog1.example.com and blog2.example.com) or subdirectories of the same domain name (e.g. example.com/blog1 and example.com/blog2) you end up having the same named cookie, on the same domain, for two different sites. If you first visit one site and then another, trying to access the second site will result in a blank page for technical reasons. We haven’t found a reliable solution yet. For the gory details, keep reading.

    If you are wondering on the technical reasons: we need to know if the logged in user is legitimate or whether there has been a cookie forgery / cookie hijacking. One of the ways we prevent that is checking the internal, numeric user ID of your WordPress user. Since this numeric ID differs from one site to the next our protection is triggered, causing the blank page. If we remove that protection we’d expose you to a minute but real security issue. Therefore we decided to let this blank page issue be at the time being until we find a way to create a reliable semi-random cookie name per site, without compromising your site’s security. We consider your security to be our top concern.

    I have the same problem. A blank screen after I install and activate the plugin. I’m not using any sub-domains, and I’ve tried switching to PHP versions 5.3, 5.4, 5.5, 5.6.

    Nothing works.

    I’m using WordPress 4.0 with a Themify theme (Magazine). I’ve tried switching to Twenty Twelve, as well as switching off all plugins. I’ve also uninstalled and re-installed the plugin after each change I made.

    It doesn’t matter what I do, the plugin just does not work. I’m not doubting the sub-domain/directory issue, but it would seem that is not the only cause of this problem.

    Plugin Author nikosdion

    (@nikosdion)

    Do you have any PHP errors in your server log? If you do, please copy them here.

    I’ll be very interested once you’ve got the domain-cookie issue figured out. I’d fiddle with it myself, but not enough hours in a day ;-/

    Plugin Author nikosdion

    (@nikosdion)

    We have already fixed that issue in the currently published version.

    Thanks nikosdion.

    I’ll give it a try very soon. If anything blows up, I’ll let you know ?? If not, I’ll let you know that too.

    Thanks again, Dave

    Hello I am having the same problem; Once you go inside Akeeba in WP 4.1, I got and empty page; no buttons, nothing: https://www.irokodoors.com/new/

    Using PHP 5.4.24.

    Any advice?

    Thanks.

    Plugin Author nikosdion

    (@nikosdion)

    As I wrote in the previous posts, first try to clear the cookies. If this doesn’t help I really do need any PHP errors you might be seeing in your server’s log.

    An empty page is a PHP error in disguise. Since I don’t get a blank page / PHP error when using the same software on a big number of different server configurations, many of which using the same PHP version as yours, I can only assume that there’s a third party plugin messing up and causing the PHP error. Either that or the PHP version you have is not the PHP version you think you have. The only way for me to know exactly what is the problem with your server or host is the error log.

    So, can you please provide me with this information?

    Hello nikosdion thanks for quick reply; below the log:

    VALUES ( ‘dddeba901a654caaa0e5e39e9f940749’, ‘1425515135’, ‘calacara’, ‘190.155.222.164’, ‘valid’, ”, ‘1’ ) made by require_once(‘wp-admin/admin.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, wppa_session_start, wppa_create_session_entry
    [05-Mar-2015 00:25:36] WordPress database error Table ‘irokodo1_wo3567.wp_fijt_wppa_session’ doesn’t exist for query INSERT INTO wp_fijt_wppa_session (
    session,
    timestamp,
    user,
    ip,
    status,
    data,
    count
    )
    VALUES ( ‘dddeba901a654caaa0e5e39e9f940749’, ‘1425515136’, ‘calacara’, ‘190.155.222.164’, ‘valid’, ”, ‘1’ ) made by require_once(‘wp-admin/admin.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘init’), call_user_func_array, wppa_session_start, wppa_create_session_entry
    [05-Mar-2015 00:29:28] PHP Warning: opendir(/home1/irokodo1/public_html/new/wp-content/gallery) [function.opendir]: failed to open dir: No such file or directory in /home1/irokodo1/public_html/new/wp-content/plugins/wp-photo-album-plus/wppa-admin-functions.php on line 423
    [05-Mar-2015 21:38:14] PHP Fatal error: Call to a member function onDeactivation() on a non-object in /home1/irokodo1/public_html/new/wp-content/plugins/grid-gallery-ready/src/GirdGallery/Installer/Module.php on line 85
    [07-Mar-2015 16:07:48] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:07:59] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:08:06] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:21:26] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:21:47] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:24:35] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:25:29] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [07-Mar-2015 16:40:02] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [08-Mar-2015 22:45:49] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [09-Mar-2015 13:35:50] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9
    [09-Mar-2015 06:46:59] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65443841 bytes) in /home1/irokodo1/public_html/new/wp-includes/functions.php on line 3269
    [09-Mar-2015 06:47:00] PHP Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 65443841 bytes) in /home1/irokodo1/public_html/new/wp-includes/functions.php on line 3269

    Plugin Author nikosdion

    (@nikosdion)

    Thank you! Exactly as I suspected all along. You DO NOT have PHP 5.4. Based on your error message you have PHP 5.2 or earlier. Please contact your host. The relevant error message that gave this away is:

    [09-Mar-2015 13:35:50] PHP Parse error: syntax error, unexpected T_STRING, expecting T_CONSTANT_ENCAPSED_STRING or ‘(‘ in /home1/irokodo1/public_html/new/wp-content/plugins/akeebabackupcore/helpers/bootstrap.php on line 9

    Line 9 has a use statement. This is syntax which was added to PHP since version 5.3.0. All earlier versions will crash with “syntax error, unexpected T_STRING” upon encountering this syntax that they are not supposed to recognise.

    Please note that the other messages do not pertain to our software as you can see from the paths in the filenames referenced in them.

    Why could your host tell you that you have PHP 5.4 but an earlier version be in effect?

    There are a few reasons:

    • The advertised PHP version is the default for new servers or accounts but you have an old account. In this case you need to enable the newer PHP version manually or by contacting your host.
    • Your host gives you a selection of PHP versions and you’ve selected a version earlier than PHP 5.3.
    • You have modified the PHP version you are using through a .htaccess, php.ini or .user.ini file in your hosting user account directory, site’s root (usually called public_html, htdocs, www or something similar), wp-content directory, wp-content/plugins directory or wp-content/plugins/akeebabackup directory. WARNING: This CAN cause different parts of your site run under different PHP versions, so a phpinfo.php file in your site’s root IS NOT a good indication of which PHP version you are using in wp-admin!!!
    • You have otherwise misread or misinterpreted your host’s information regarding the use of PHP versions

    In all cases, if unsure please contact your host. As we documented and forewarned you in the plugin’s description, our plugin REQUIRES PHP 5.3.04 or later.

    You are great, nikosdion!

    cPanel displays PHP 5.4.24., but further checking with a script revealed the actual version is PHP 5.2.17

    Thanks for your fine and quick advice.

    Plugin Author nikosdion

    (@nikosdion)

    You’re welcome! This kind of issues are quite common ??

Viewing 14 replies - 1 through 14 (of 14 total)
  • The topic ‘No Configuration Button’ is closed to new replies.