SeanTodd

Sorry Stefano – found the reference on the www.ads-software.com download “Install” tab:

Installation:

Once installed you can start to use the [includeme] shortcode to include external file in your posts or pages.
See the official page for example and options.
The inclusion folder is initially set to WP_CONTENT_DIR/include-me. You can change it with a define(‘INCLUDE_ME_DIR’, ‘…’) in your wp-config.php.
If you want to enable the old behavior and be able to include from any location, use define(‘INCLUDE_ME_DIR’, ‘*’).`

Worked perfectly!

Sean

Stefano,

We tried to update to 1.3, but it breaks our 1.2.1 version since all of our PHP files are in the root of the site. You mentioned “I’ll add the option to define a constant in the wp-config.php file to change the folder (and if it’s allowed to unlock the folder constraint).” – Is that an option? I don’t see that in your current documentation.

If not, is there a place to download version 1.2.1?

Thanks!
Sean

I am having the same issue with the Elated Borderland (https://demo.elated-themes.com/borderland1/) WordPress theme. Just letting you know to help you track down the problem.

Do you have any suggestions in the meantime? If I install another plugin, like Yoast, I will have to re-enter all of my descriptions.

This just recently is an issue… I have been using your plugin for a while now, and it used to work fine. Something recently has introduced the shortcodes into the descriptions.

We are using the Borderlands theme version 1.8, and they have a version 1.13 version available. Version 1.9 has a comment “Fixed Social Share Functionality” – I am going to try to update the theme… to see if that might fix the problem.

Maybe this will help Marty with his issue…

Have there been any other developments with this issue? It is obviously not the “set_time_limit(7200);” wpconfig setting that is going to solve this problem.

Is there anything else to try related to the time limit? The backup still fails after just a few moments – not the entire time limit set by the variable.

If there are other PHP settings that are related that you would recommend trying, I am willing to test them for you.

Thx.

I had the php timeout set at 1800 – and increased it to 3600 and 7200 seconds (that’s two hours!) – The process ends after a few minutes (4 or 5 minutes) with an error:

PHP EXECUTION TIMEOUT ERROR
Your hosting has an execution time limit of 7200 seconds for PHP scripts, which is not enough for performing full backup/restore of your website. A full website backup/restore is a complex process which may take a couple of minutes depending on many circumstances. The needed execution time varies depending on the backup options and your server performance, that’s why we cannot tell exactly how much execution time is needed. But, almost all hosting providers give users the ability to increase the execution time limit or they increase it themselves, upon user request. Please ask your hosting provider if they are able increase your execution time limit.
————————–
Here is the log:

Date: 2016-03-16 21:14
SG Backup version: 1.1.1
OS: Linux
Server: Apache
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
PHP version: 5.5.33
SAPI: cgi-fcgi
Codepage: C
Int size: 4
Int lib: bcmath
Memory limit: 256M
Max execution time: 7200
Environment: WordPress 4.4.2
Backup type: files,database

2016-03-16 21:14: Start backup
2016-03-16 21:14: Start backup database
2016-03-16 21:14: Total tables to backup: 16
2016-03-16 21:14: Total rows to backup: 11730
2016-03-16 21:14: Start backup table: j8mmzs62ovcommentmeta
2016-03-16 21:14: End backup table: j8mmzs62ovcommentmeta
2016-03-16 21:14: Start backup table: j8mmzs62ovcomments
2016-03-16 21:14: End backup table: j8mmzs62ovcomments
2016-03-16 21:14: Start backup table: j8mmzs62ovduplicator_packages
2016-03-16 21:14: End backup table: j8mmzs62ovduplicator_packages
2016-03-16 21:14: Start backup table: j8mmzs62ovduplicator_pro_entities
2016-03-16 21:14: End backup table: j8mmzs62ovduplicator_pro_entities
2016-03-16 21:14: Start backup table: j8mmzs62ovduplicator_pro_packages
2016-03-16 21:14: End backup table: j8mmzs62ovduplicator_pro_packages
2016-03-16 21:14: Start backup table: j8mmzs62ovlayerslider
2016-03-16 21:14: End backup table: j8mmzs62ovlayerslider
2016-03-16 21:14: Start backup table: j8mmzs62ovlinks
2016-03-16 21:14: End backup table: j8mmzs62ovlinks
2016-03-16 21:14: Start backup table: j8mmzs62ovoptions
2016-03-16 21:14: End backup table: j8mmzs62ovoptions
2016-03-16 21:14: Start backup table: j8mmzs62ovpostmeta
2016-03-16 21:14: End backup table: j8mmzs62ovpostmeta
2016-03-16 21:14: Start backup table: j8mmzs62ovposts
2016-03-16 21:17: SGExceptionExecutionTimeError: Execution timeout error [File: /wp-content/plugins/backup/com/core/backup/SGBackup.php, Line: 106, URL: /wp-admin/admin-ajax.php]

Are we chasing a rabbit here? At two hours, there should be more than enough time for the process to complete. In other sites where I use Backup Guard, the total backup rarely takes more than 5-10 minutes (at worst)…

Is it possible there is another php config setting that is the real cause? I can contact the hosting provider, but would need to be specific.

Heather – it is not resolved. I’m still seeing the same issue. The strange thing is, I have this plugin installed on several other sites, and it works beautifully. This is the only site where it fails. It must be some incompatibility with the hosting environment, but I do not know the cause. Changing the timeout did nothing.

Closer still… but an even odder log file this time…

It very quickly (a second or tw0) went to 69% (the popup hint when mousing over the progress bar indicated “Backup Database – 69%”) and stayed like that for a couple of minutes. Eventually it indicated a failure, and the backup log seems truncated…

Date: 2016-02-22 20:19
SG Backup version: 1.1.1
OS: Linux
Server: Apache
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
PHP version: 5.5.30
SAPI: cgi-fcgi
Codepage: C
Int size: 4
Int lib: bcmath
Memory limit: 256M
Max execution time: 1800
Environment: WordPress 4.4.2
Backup type: files,database

2016-02-22 20:19: Start backup
2016-02-22 20:19: Start backup database
2016-02-22 20:19: Total tables to backup: 16
2016-02-22 20:19: Total rows to backup: 11268
2016-02-22 20:19: Start backup table: j8mmzs62ovcommentmeta
2016-02-22 20:19: End backup table: j8mmzs62ovcommentmeta
2016-02-22 20:19: Start backup table: j8mmzs62ovcomments
2016-02-22 20:19: End backup table: j8mmzs62ovcomments
2016-02-22 20:19: Start backup table: j8mmzs62ovduplicator_packages
2016-02-22 20:19: End backup table: j8mmzs62ovduplicator_packages
2016-02-22 20:19: Start backup table: j8mmzs62ovduplicator_pro_entities
2016-02-22 20:19: End backup table: j8mmzs62ovduplicator_pro_entities
2016-02-22 20:19: Start backup table: j8mmzs62ovduplicator_pro_packages
2016-02-22 20:19: End backup table: j8mmzs62ovduplicator_pro_packages
2016-02-22 20:19: Start backup table: j8mmzs62ovlayerslider
2016-02-22 20:19: End backup table: j8mmzs62ovlayerslider
2016-02-22 20:19: Start backup table: j8mmzs62ovlinks
2016-02-22 20:19: End backup table: j8mmzs62ovlinks
2016-02-22 20:19: Start backup table: j8mmzs62ovoptions
2016-02-22 20:19: End backup table: j8mmzs62ovoptions
2016-02-22 20:19: Start backup table: j8mmzs62ovpostmeta
2016-02-22 20:19: End backup table: j8mmzs62ovpostmeta
2016-02-22 20:19: Start backup table: j8mmzs62ovposts

I submitted the ticket – thank you for your assistance!

Sean.

Some progress with the 1.0.4 version… Now, the status bar shows up, fills out for about 1/5 the width, they displays an error… the entire process only lasts for about 20-30 seconds. Much better than before where it fails almost immediately.

Date: 2016-02-19 16:01
SG Backup version: 1.1.1
OS: Linux
Server: Apache
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
PHP version: 5.5.30
SAPI: cgi-fcgi
Codepage: C
Int size: 4
Int lib: bcmath
Memory limit: 256M
Max execution time: 1800
Environment: WordPress 4.4.2
Backup type: files,database

2016-02-19 16:01: Start backup
2016-02-19 16:01: Start backup database
2016-02-19 16:01: Total tables to backup: 16
2016-02-19 16:01: Total rows to backup: 11159
2016-02-19 16:01: Start backup table: j8mmzs62ovcommentmeta
2016-02-19 16:01: End backup table: j8mmzs62ovcommentmeta
2016-02-19 16:01: Start backup table: j8mmzs62ovcomments
2016-02-19 16:01: End backup table: j8mmzs62ovcomments
2016-02-19 16:01: Start backup table: j8mmzs62ovduplicator_packages
2016-02-19 16:01: End backup table: j8mmzs62ovduplicator_packages
2016-02-19 16:01: Start backup table: j8mmzs62ovduplicator_pro_entities
2016-02-19 16:01: End backup table: j8mmzs62ovduplicator_pro_entities
2016-02-19 16:01: Start backup table: j8mmzs62ovduplicator_pro_packages
2016-02-19 16:01: End backup table: j8mmzs62ovduplicator_pro_packages
2016-02-19 16:01: Start backup table: j8mmzs62ovlayerslider
2016-02-19 16:01: End backup table: j8mmzs62ovlayerslider
2016-02-19 16:01: Start backup table: j8mmzs62ovlinks
2016-02-19 16:01: End backup table: j8mmzs62ovlinks
2016-02-19 16:01: Start backup table: j8mmzs62ovoptions
2016-02-19 16:01: End backup table: j8mmzs62ovoptions
2016-02-19 16:01: Start backup table: j8mmzs62ovpostmeta
2016-02-19 16:02: SGExceptionExecutionTimeError: Execution timeout error [File: /wp-content/plugins/backup/com/core/backup/SGBackup.php, Line: 105, URL: /wp-admin/admin-ajax.php]
2016-02-19 16:02: End backup table: j8mmzs62ovpostmeta
2016-02-19 16:02: Start backup table: j8mmzs62ovposts

Same results with the new execution time of 1800…

I think it is important to note that the failure happens almost immediately (within 10 seconds), so there might be another cause.

Date: 2016-02-18 16:53
SG Backup version: 1.1.1
OS: Linux
Server: Apache
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
PHP version: 5.5.30
SAPI: cgi-fcgi
Codepage: C
Int size: 4
Int lib: bcmath
Memory limit: 256M
Max execution time: 1800
Environment: WordPress 4.4.2
Backup type: files,database

2016-02-18 16:53: Start backup
2016-02-18 16:53: Start backup database
2016-02-18 16:53: Total tables to backup: 16
2016-02-18 16:53: Total rows to backup: 11003
2016-02-18 16:53: Start backup table: j8mmzs62ovcommentmeta
2016-02-18 16:53: End backup table: j8mmzs62ovcommentmeta
2016-02-18 16:53: Start backup table: j8mmzs62ovcomments
2016-02-18 16:53: End backup table: j8mmzs62ovcomments
2016-02-18 16:53: Start backup table: j8mmzs62ovduplicator_packages
2016-02-18 16:53: End backup table: j8mmzs62ovduplicator_packages
2016-02-18 16:53: Start backup table: j8mmzs62ovduplicator_pro_entities
2016-02-18 16:53: End backup table: j8mmzs62ovduplicator_pro_entities
2016-02-18 16:53: Start backup table: j8mmzs62ovduplicator_pro_packages
2016-02-18 16:53: End backup table: j8mmzs62ovduplicator_pro_packages
2016-02-18 16:53: Start backup table: j8mmzs62ovlayerslider
2016-02-18 16:53: End backup table: j8mmzs62ovlayerslider
2016-02-18 16:53: Start backup table: j8mmzs62ovlinks
2016-02-18 16:53: End backup table: j8mmzs62ovlinks
2016-02-18 16:53: Start backup table: j8mmzs62ovoptions
2016-02-18 16:53: End backup table: j8mmzs62ovoptions
2016-02-18 16:53: Start backup table: j8mmzs62ovpostmeta
2016-02-18 16:53: End backup table: j8mmzs62ovpostmeta
2016-02-18 16:53: Start backup table: j8mmzs62ovposts
2016-02-18 16:53: SGExceptionServerError: Execution time abort [File: /homepages/33/d70125866/htdocs/clickandbuilds/WordPress/MyCMS2/wp-content/plugins/backup/com/core/functions.php, Line: 157, URL: /wp-admin/admin-ajax.php]

I increased the time to 300 in the wpconfig file, and it still failed… just how long should the execution time be? I would have thought 5 minutes to be sufficient…

Date: 2016-02-18 15:00
SG Backup version: 1.1.1
OS: Linux
Server: Apache
User agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:44.0) Gecko/20100101 Firefox/44.0
PHP version: 5.5.30
SAPI: cgi-fcgi
Codepage: C
Int size: 4
Int lib: bcmath
Memory limit: 256M
Max execution time: 300
Environment: WordPress 4.4.2
Backup type: files,database

2016-02-18 15:00: Start backup
2016-02-18 15:00: Start backup database
2016-02-18 15:00: Total tables to backup: 16
2016-02-18 15:00: Total rows to backup: 11003
2016-02-18 15:00: Start backup table: j8mmzs62ovcommentmeta
2016-02-18 15:00: End backup table: j8mmzs62ovcommentmeta
2016-02-18 15:00: Start backup table: j8mmzs62ovcomments
2016-02-18 15:00: End backup table: j8mmzs62ovcomments
2016-02-18 15:00: Start backup table: j8mmzs62ovduplicator_packages
2016-02-18 15:00: End backup table: j8mmzs62ovduplicator_packages
2016-02-18 15:00: Start backup table: j8mmzs62ovduplicator_pro_entities
2016-02-18 15:00: End backup table: j8mmzs62ovduplicator_pro_entities
2016-02-18 15:00: Start backup table: j8mmzs62ovduplicator_pro_packages
2016-02-18 15:00: End backup table: j8mmzs62ovduplicator_pro_packages
2016-02-18 15:00: Start backup table: j8mmzs62ovlayerslider
2016-02-18 15:00: End backup table: j8mmzs62ovlayerslider
2016-02-18 15:00: Start backup table: j8mmzs62ovlinks
2016-02-18 15:00: End backup table: j8mmzs62ovlinks
2016-02-18 15:00: Start backup table: j8mmzs62ovoptions
2016-02-18 15:00: End backup table: j8mmzs62ovoptions
2016-02-18 15:00: Start backup table: j8mmzs62ovpostmeta
2016-02-18 15:00: End backup table: j8mmzs62ovpostmeta
2016-02-18 15:00: Start backup table: j8mmzs62ovposts
2016-02-18 15:00: SGExceptionServerError: Execution time abort [File: /homepages/33/d70125866/htdocs/clickandbuilds/WordPress/MyCMS2/wp-content/plugins/backup/com/core/functions.php, Line: 157, URL: /wp-admin/admin-ajax.php]