Timothy Wood

That looks like an interesting challenge. I’d have to give some thought to that example since in theory your example of property-106 in someone’s install might be the 106th time it has been duplicated. The way this plugin works is based off your page title thus if a dup exists it will default to WordPress’ mechanisms for handling conflicting slugs.

I have logged this in my issue tracker for the plugin to possibly address in a future release https://github.com/codearachnid/wp-reset-slug/issues/1

Thank you for submitting an interesting challenge.

oh derp forgot to add it in the comment. Tim [at] imaginesimplicity.com

That’s odd you do not have any js error. I still have not been able to replicate locally. If you don’t mind emailing me credentials for your site where I can take a look directly and see what might be causing a conflict on that specific page in the admin?

Can you look at the page in chrome with Developer Tools active and see if there are any JavaScript errors in the console?

Thanks to @mathijsbok for generously providing access to debug issues, I have completely refactored how attachments are attached to the notification based on an issue where some servers return a blank array when using wp_get_attachment_meta. By utilizing wp_get_attachment_url and replacing the url with the base path it ensures that the attachment file is included if valid. Please upgrade to version 1.2 to take advantage of this update.

Mathijsbok this sounds very interesting, I’ve sent you an email to follow up on this.

That’s great! I’m glad it was able to save you time as well.

A new version has been released that fixes the issues brought up by the support forum. Please let me know if there are still residual issues.

@mathijsbok, would you be available to discuss this directly? Please contact me via twitter.com/codearachnid and I can send you private contact information. I have some tests outside of WordPress that can be run on your host and determine if it’s the email, server, code or WordPress that is failing to deliver the attachments.

@jan, thank you for the update. Your issue should be fixed in the latest version update.

A new version has been released that fixes the issues brought up by the support forum. Please let me know if there are still residual issues.

Brian,

Thank you for leaving a review of the plugin and articulating the issue you’re having. I just pushed a hotfix to the issue you and several other in the forums seemed to be having. If you would like bleeding edge code please do not hesitate to checkout https://github.com/codearachnid/gf-notification-attachment. I appreciate any improvements you can recommend (pull request or issue tracking).

Please let me know if this latest version fixes the issue you are having.

Cheers,
Tim

@mathijsbok, Please ensure that your server isn’t blocking the sending of attachements (I have found a lot of shared server environments restrict mail that may contain attachments). If this is the case I would recommend using a custom SMTP server to route your email and a plugin like WP SMTP or similar to configure.

Your second question about who recieves the attachment. I would assume you could setup several notification emails – one to the client adn the other to the reciever. The email to the client would then include the PDF.

Great! Thank you for the followup.

replace your line 129 with the following:

$image = wp_get_attachment_image_src( $attachment_id, array(100,100), true );
        if( !empty( $image ) )
                $image = $image[0];

mathijsbok, it seems you’re having the same error as identified already. Please ensure that the code is updated on your server.

Hello Marloes, I was looking at the disallowed plugin list on WP Engine’s website https://wpengine.com/support/disallowed-plugins/. It seems that sending email from the server might be included in that. Do you have a plugin like WP SMTP for sending mail from your own email servers?

Cheers,
Tim