ehau

So if there is a fix, should this plugin be updated with this fix?

I can confirm that if you install bleeding edge/beta Gutenberg separate plugin, then the patterns are not shown in the Inserter any more.

I think they actually are created, but the new gutenberg does not show them

Would it be possible to temporarily modify the code in /dynamo/src/mo-reader.php to output the name of the problematic file and perhaps some other debug info in the log warning?

Would you have and example how this code could look like?

• This reply was modified 2 years, 11 months ago by ehau.
• This reply was modified 2 years, 11 months ago by ehau.

Isn’t there easily a large amount of these mo-files?

Any suggestions how to identify the problem. Maybe disable plug-ins one by one with wp cli? Or just check the logs?

Same here.
So basically Sucuri creates log files that grow and grow until they are so big that Sucuri scan runs out of memory because it tries to scan its own log file for malware.

Currently I had to delete these log files from time to time (manually or by script) to keep the system running.

This should be fixed right away!

Alright so apparently our developer had installed the PRO version, hence the version 4.0.3, which has this OAuthException mentioned above.

Workaround is to first click the Authorize button and then edit the URL and remove the &scope=basic+public_content in the end

Almost the same error when clicking the green “Authorize” button next to Instagram in the Version 4.0.3.

Strangely the newest version right now at https://www.ads-software.com/plugins/flow-flow-social-streams/ is 3.1.66, but apparently WP has managed to update to 4.0.3.

Version 4.0.3 does not have the method2 anymore and clicking the green “Authorize” causes error below and its currently the newest version apparently

the 3.1.66 Installed on test site is called Flow-Flow Lite while the 4.0.3 on live site is called only Flow-Flow in the plugin list.

{“error_type”: “OAuthException”, “code”: 400, “error_message”: “Invalid scope field(s): basic,public_content”}

I just got the same error message.

The site seems to load fine over HTTPS.

I’m experiencing the same

…and after hours of scratching my head I solved it.

I had copied some text from another website to a text editor widget. It also had copied some HTML with it, so I had extra </div> in there.

SUGGESTION for Elementor team:
Please check in all inputs that HTML code is closed properly and at least give a warning!

This worked for me (from 3rd-party Integration Github Issues)
It’s based on the maybe outdated MailChimp example
https://github.com/zaus/forms-3rdparty-integration/issues/74#issuecomment-260978289

I modified it slightly and added and modified some comments:

if(!class_exists('Forms3rdParty_Callbacks')):
/**

Encapsulate any and all 3rd-party service callback functions
*/
class Forms3rdParty_Callbacks {
public function __construct(){

// actions require 2 parameters: 3rd-party response, results placeholders
// NOTE: customize this hook name to match your Service (in the admin settings)
// or use Forms3rdPartyIntegration_service to affect all the forms
add_action('Forms3rdPartyIntegration_service', array(&$this, 'forms3rdParty_action'), 10, 2);
}//-- function __construct
/**
@Param $response the remote-request response
@Param $results
*/
public function forms3rdParty_action($response, $results){
try{
// look once more for success message, in case someone didn't set up the success clause
if( false !== strpos($response, '"status":"ok"') ) :
// Decode the received JSON to array
$response_json = json_decode($response, true);
//after converting to array output a certain json value (for example "description") to the success message next to the form on page, or whatever it might be in your case
$results['message'] = 'Success! The response;' $response_json["description"];
//This is used for adding things to mail (if sent)
$results['attach'] = $response;
else:
$results['errors'] = array('Failed');
endif;

} catch(Exception $ex){
$results['errors'] = array($ex->getMessage());
}

}//-- function 3rdParty_action

}//--- class Forms3rdParty_Callbacks
//start 'em up
$Forms3rdPartycallback_instance = new Forms3rdParty_Callbacks();
endif; //class-exists

Could you elaborate just a little bit more?

I’m able to change the success message with a function but struggling to understand how to output the error or failure response message that is, depending on the API, in raw or json format, for example:

Raw:
Error: Insert failed, duplicate id

Json:
{
“status”:”ok”,
“customer_id”:11264904,
“instructions”:”Go to your app and enter the given number”
“number”:”1234″
}

How would I output that error message or the “instructions” and “number” fields to user?

Thank you!

Maybe a simple check for some variables would lower the burden of answering so many support request of similar type? ??

Problem turned out to be the line:

define(‘WP_CONTENT_URL’, ‘/wp-content’);

Commenting this out fixes the problems.

The default constant for this is:
define( ‘WP_CONTENT_URL’, get_option(‘siteurl’) . ‘/wp-content’);

So a relative WP_CONTENT_URL does not work apparently

For the reference I’m using Microsoft Azure server that runs a docker container, that provided a slightly tuned wp-config for the cloud environment.

I did some quick digging in the wp-config and found this in the last lines, I had not noticed before:

//Relative URLs for swapping across app service deployment slots 
define('WP_HOME','https://'. filter_input(INPUT_SERVER, 'HTTP_HOST', FILTER_SANITIZE_STRING));
define('WP_SITEURL','https://'. filter_input(INPUT_SERVER, 'HTTP_HOST', FILTER_SANITIZE_STRING));
define('WP_CONTENT_URL', '/wp-content');
define('DOMAIN_CURRENT_SITE', filter_input(INPUT_SERVER, 'HTTP_HOST', FILTER_SANITIZE_STRING));
/** Absolute path to the WordPress directory. */
if ( !defined('ABSPATH') )
	define('ABSPATH', dirname(__FILE__) . '/');
/** Sets up WordPress vars and included files. */
require_once(ABSPATH . 'wp-settings.php');

I have not had time to test stripping that away for a moment, or overriding with a traditional config, but looks like a suspect to me.