redesigned

This is for the Instagram feed plugin, not the Facebook feed plugin.

Checking that the variables are arrays before calling array_merge would prevent the error from being thrown.

I’ll open a support ticket at the suggested location.

yes, BUT when building a purely gutenberg theme, using block template wp_template post type to theme slug mapping, so that you don’t have any php template files, what gutenberg block should be use to build the search results page of a site?

Hooking this:
https://github.com/WordPress/gutenberg/pull/13583

It seems this will be it:
https://github.com/WordPress/gutenberg/pull/20106
but that it isn’t completed yet, so we’ll have to build out own block in the meantime,, unless anyone knows otherwise.

Pure gutenberg sites are so close, this is the last piece.

Got it working by deactivating a 3rd party pagebuilder widget library. Sorry for the bother. ??

I’m also seeing false positives when searching wp_postmeta or other tables with serialized data. since i can’t see what it is matching and have no way to select or unselect which matches to act on, there is no way i can run the search and replace without fear of replacing false matches and corrupting data. ??

on the current site i get 41 matches on wp_postmeta for any term or string i know doesn’t exist.

anyone have any ideas?

Having the same issue.

1. wp-content directory is writable (755), wordpress writes content all the time.

2. in wp-config

define('WP_DEBUG', true);
define('WP_DEBUG_LOG', true);
define('WP_DEBUG_DISPLAY', false);
@ini_set('display_errors',0);
@ini_set("error_log", dirname(__FILE__).'/wp-content/debug.log');

3. manually trying to write custom logs
error_log('#test: Test.');

4. Error:
Debugging is enabled. However, the debug.log file does not exist or was not found.

Any Ideas?

update #1: if i manually create the debug.log file the plugin finds it and shows 0 errors. but still no luck writing to it.

update #2: think i found the issue. if i run phpinfo the error_log location is being overridden by the server and @ini_set isn’t overwriting it. neither is php.ini or .user.ini. looks like this is hard set in the server config and not user changeable.

SOLUTION: since I couldn’t change the error_log location, i created a symlink from the location and filename the plugin is expecting to the actual location and file. The logging now appears to be working as expected. Hope this helps someone in the future with the same issue. cheers.

Any Ideas?

• This reply was modified 8 years, 1 month ago by redesigned.
• This reply was modified 8 years, 1 month ago by redesigned.
• This reply was modified 8 years, 1 month ago by redesigned. Reason: solution

Duh. Had to switch the homepage from using the home page to display latest posts, working now.

I’m having the same issue on several installs, works fine on others. Normal backup jobs with all the default options. No clue why this error is occurring, but the backup file is small and doesn’t contain any of the actual files…

Did you ever get to the bottom of this issue or find an alternative?

did you ever figure this out? i am trying to do something similar.

resolved.

Figured it out myself…haha.

If i don’t check the box to download the file to my computer, then it saves the file just fine and i can then click the link from the notice message and download it.

Not sure why it works in two steps but not in one, but i’m glad it is working.

Thanks again for the great plugin!

Hi Brad,

I just wanted to post back that I figured out the issue.

The file download is passed through a php file instead being a direct download. For some reason the way the php file checks the admin login cookie it doesn’t work with several of the major download managers for firefox even though they pass the same cookie.

Confirmed not working through: FlashGot, DownThemAll, Leech…probably most.

If you disable the download manager, you no longer download the wp-login.php file itself.

Hope that helps.

Thanks,
Josh

they both only use the image-widget and the wysiwyg-text widgets. neither has any other plugins, they are both pretty basic sites.

maybe an incompatibility with wp-migrate-db and certain server configurations?

sorry i wish i had more info about a possible cause, i know this bug report isn’t a lot of help without more info or a way to reproduce. Has anyone else reported this issue?

Both these sites are already moved from those locations to new locations, which is why i was trying to use your plugin, or else i’d try and get you access info.

when i run wp-migrate to generate the new sql file for migration, instead of creating the file i needed, it triggers the borwser to download the wp-login.php file.

this was happening on a client hosted on hostgator.
it also happened a week later on a client hosted on a IIS server.

normally wp-migrate-db works like a champ, but for some reason in certain cases it doesn’t generate the files and rather spits out the login php file as a download instead, even though you have to already be logged in in order to run wp-migrate-db.

does that make sense?

I too am curious if this plugin handles wp serialized data as that is the main reason i’d have for such a plugin.

moving datatbases, copying files, updating wp-config.php and the wp_options table are no problem manually.

It is the darn serialized data and all the widgets and plugins that use serialized data and the embedded string length that is the pain. ??

If this plugin properly handles serialized data like wp_migrate_db then it looks like a real find. If not then it will cause a lot of missing data, widgets, and plugins, and needs to be updated for the new way wordpress saves serialized data.

Thanks.