[e2pdf-save] custom directory no longer working

This is no longer working for me on one of my sites.
[e2pdf-save id="1" name="[512] [513] [id]" dir='wp-content/uploads/formidable/[118 show="user_email"]/' create_dir="true" overwrite="true"]
I even tried the following to be a bit simpler
[e2pdf-save id="1" name="[512] [513] [id]" dir="wp-content/uploads/formidable/" create_dir="true" overwrite="true"]
but no difference...

When i do this though
[e2pdf-save id="1" name="[512] [513] [id]"]
it goes to the default directory

Anyone know what has changed in the most recent version?

Hi,

Can you try please to use following shortcode:

[e2pdf-save id="1" name="[512] [513] [id]" dir='wp-content/uploads/[118 show="user_email"]/' create_dir="true" overwrite="true"]

If it will work and it will create user email dir under uploads folder with PDF it can be permission issue.

If it will not work, try to use full path to dir as:

[e2pdf-save id="1" name="[512] [513] [id]" dir='/home/user/.../wp-content/uploads/formidable/[118 show="user_email"]/' create_dir="true" overwrite="true"]

You can find path by enabling "debug" mode at "E2Pdf" -> "Settings". And navigate to "E2Pdf" -> "Debug".

P.s. It was some bug fixes to current function, however they were released long time ago.

We remain at your service.

---

We would really appreciate your feedback at WordPress.org!

[e2pdf-save id="1" name="[512] [513] [id]" dir='/www/wp-content/uploads/formidable/[118 show="user_email"]/' create_dir="true" overwrite="true"]

worked when i done that and added www

strange when i downgraded to a version that is working on other sites it didn't work with the old way though.

I will make the www change on other sites with old version too though too future proof them of issues.

Might be worthwhile adding the www to your documentation as well cause the dir doc at the moment specifies only wp-content

thanks :)

Thank you for letting us know. Currently your old shortcode must work, however maybe it was changed something with WordPress like multisite or by hosting provider which gives incorrect root path of WordPress installation. We will do further tests to be sure that it's not WordPress core changes.

We remain at your service.

---

We would really appreciate your feedback at WordPress.org!