horizonm

hello. I am a WPMUdev member and I am also complaining about this. Yes, the email will render in 99% of readers, but it increases the SPAM score just as John-Pierre was describing. On one site, an email wasn’t being delivered and this is what seemed to be pushing the score over the edge.

Patrick, I checked the “roadmap” and there is no indication this is on the bug fix list and I’m currently using 1.15.2.

Can you indicate specifically where this issue is within the roadmap?

I’m experiencing the problem as well. When I look at the original message in Gmail, I see that it is doubly escaping the quotes in the From field.

IE, if I enter Joe in the From name, it comes through as “\”Joe”\”.

Not sure what’s causing that escaping. Hopefully admin will chime in.

Note – there was some incorrect HTML in the code sample – a strong tag got in there:

$current_theme_has_uc_page = file_exists(get_template_directory() . '/under-construction.php');

and I could have pasted the code per my suggestion to replace it with:

$current_theme_has_uc_page = file_exists(get_stylesheet_directory() . '/under-construction.php');

another option may be to use a phar distribution of the aws library to minimize number of files:

https://docs.aws.amazon.com/aws-sdk-php/v2/guide/installation.html#installing-using-the-php-archive-phar

Just FYI, would be nice to get this resolved. In the v 1.9, it seems that some folders in the AWS toolkit are simply missing.

The code in:
static-html-output-plugin/library/aws/aws-autoloader.php

On lines 720 through 733 look for files in:
static-html-output-plugin/library/aws/Aws/S3/Enum/

And the Enum folder is non-existent in the current distribution.

Is it possible to just include that folder and publish a 1.9.1 or something?

Thanks for letting us know that this change will be made. Any idea of the implementation time period?

hey Alin,

I was just following up on this. I know it’s marked as resolved, but is it available in the current 4.9.6.2 version, or are we still waiting for the 5 release. I note the last post was about 6 weeks ago and you had stated a couple of weeks before the release… do you mind giving a new ETA?

Look so forward to this feature. I’ve been using this plugin for years now, on all of my sites. One and only!

Thanks,

Joe

That line uses a feature called “anonymous functions” which was added to PHP 5.3.0 so your PHP version is out of date.

I discovered this myself today on one of my sites that “broke” once I updated the SNAP plugin. Looks like it’s part of the progress updates NextScripts is implementing to be more compatible with PHP 7. I’m working with my hosting provider to update my version of PHP as it is really old anyway in order to solve the problem.

Hello lulu_,

I am having the same problem with my site. You said it disables itself it there is a posts loop in the page. Can you tell me the line number that the code is happening on? I would like to look into a patch for this to send to the developer and it will save time if you already have the location.

Otherwise, I hope to hear from the developer.

Joe

By commenting out the line, it kind of defeats the purpose of providing a template structure for the parent of a child theme framework. I had the same issue, and I added the following code to my child theme’s functions.php file.

add_action( 'after_setup_theme', 'hmw_fix_twentyten_titles' );
function hmw_fix_twentyten_titles () {
	remove_filter( 'wp_title', 'twentyten_filter_wp_title');
}

This will run after the filter is added in twentyten’s functions.php, but still in time to remove the filter itself.

Ultimately, it would be best for twentyten to change the code and either (a) make a flag/define on whether to use their built-in “SEO” or (b) make the ‘twentyten_filter_wp_title’ pluggable. The latter seems like the better option for a child theme framework.

Maybe in a future version they will wrap the function with:

if ( ! function_exists( 'twentyten_filter_wp_title' ) ) :

...CURRENT CODE GOES HERE...

endif;

Joe

It seems to me that the code from the Dashboard Widgets API is fairly clear in how to remove core dashboard widgets. It’s not as simple as saying “remove dashboard widget”, but it’s still possible using a themes files rather than modifying the core.

See:
https://codex.www.ads-software.com/Dashboard_Widgets_API

See the section “Advanced: Removing Dashboard Widgets”. Code copied is followed:

// Create the function to use in the action hook

function example_remove_dashboard_widgets() {
	// Globalize the metaboxes array, this holds all the widgets for wp-admin

	global $wp_meta_boxes;

	// Remove the quickpress widget

	unset($wp_meta_boxes['dashboard']['side']['core']['dashboard_quick_press']);

	// Remove the incomming links widget

	unset($wp_meta_boxes['dashboard']['normal']['core']['dashboard_incoming_links']);
} 

// Hoook into the 'wp_dashboard_setup' action to register our function

add_action('wp_dashboard_setup', 'example_remove_dashboard_widgets' );

It would be nice to have a complementary function to the “wp_add_dashboard_widget” function called “wp_remove_dashboard_widget”. Maybe that will be in a future release.