tmargot

Hi @prantikv,

I ran into the same problem. What I have recently used is the following together which is actually way more flexible and powerful than Email before download:

1. Gravity Forms https://www.gravityforms.com/
2. Download Monitor https://www.download-monitor.com/
3. Gravity Forms Lock https://www.download-monitor.com/extensions/gravity-forms/

The one thing I found that it could not do that I required was to capture the form details with each download. As with this, if you set it up so, your visitor only needs to fill a form once on your website and all configured downloads on whatever page they reside will be available. Gravity is super powerful but it is an annual fee?

Good luck

Same problem here, upgraded all today (WordPress, ACF, Yoast) and ended up with same error.

Oh forgot, I can confirm that the update has fixed my last reported bug. Thanks again.

Cheers,
Tris

Hiya Matt,

Great news about v2.0.2, I will be updating immediately. Only a pleasure to help out and thank you again for the plugin and amazing support/response time.

Thanks for the answer to my plugin question and the link. I do not know how I missed the article as I thought that I had scoured the ACF website top to bottom.

Take care,
Tris

• This reply was modified 7 years, 3 months ago by tmargot.

Hi Matt,

I hope this finds you well? I think I have come across another bug. I have some Option Page custom fields (https://www.advancedcustomfields.com/resources/options-page/). I had these in place prior to using your plugin. I had some existing entries in a repeater prior to using your plugin. I have since added a Font Awesome column and was successfully able to assign icons to existing repeater rows. The issue is similar to the last issue where if I try add an additional repeater row, an unrelated field becomes the Font Awesome field.

In my current situation I have a contact details repeater with a Title, Type (to select the type of contact), Email, Phone, Website URL and Font Awesome Icon field. Now when I add a row, the Type field becomes the Font Awesome Icon field.

See Screenshot

Cheers,
Tris

• This reply was modified 7 years, 3 months ago by tmargot.

Matt,

May I ask you how you got started creating an Advanced Custom Field plugin? I have looked all over for some documentation and come up with nothing ??

Cheers,
Tris

Hi Matt,

No worries, only a pleasure. Thanks for all your efforts. Initial install and test, all seems great. I will keep you posted as I am working on this project for the next week or so.

Cheers,
Tris

Hi Matt,

I think I have discovered a bug which prevents me adding Clone fields. If I try add a clone field and attempt to select an existing field to clone, the list has font-awesome icons listed (missing the icons as it is in the admin default font). When I deactivate version 2 of the plugin the problem disappears. I have quadruple checked my findings. I have temporarily gone back to Version 1.7.4 for now as it works.

Cheers,
Tris

Hi Matt,

Sorry I did not mean to be rude, but I was pulled away from WordPress for a couple days. I have only now managed to actually give it a decent test and report back. Good news, all seems to be working perfectly.

I will be working with it over the next couple weeks on my project and will report back any problems I may encounter, but as it stands it seems solid. Thank you very much for this and reaching out. If there is anything else, just let me know.

Take care,
Tris

Hi Matt,

No problem. Just got home from work and gave it a test, all working now. Thanks very much. Take care.

Cheers,
Tris

Hi Matt,

I have disabled all plugins, I only had Duplicate Post plugin installed anyway. I
then downloaded the plugin again from the bottom of the page with Development Version selected from the dropdown and still the same. Could it be the download? I know this may sound ridiculous but have you tried downloading it from the site and installing it?

I am also using the latest WordPress and the latest ACF as of today!

I also updated Chrome this morning and for some reason my Console was filtered?? So have now noticed that I am still getting the javascript error.

Uncaught TypeError: Cannot read property 'slice' of undefined
    at d.a.removePlaceholder (select2.full.min.js?ver=4.0:2)
    at d.j [as removePlaceholder] (select2.full.min.js?ver=4.0:1)
    at d.a.append (select2.full.min.js?ver=4.0:2)
    at d.j [as append] (select2.full.min.js?ver=4.0:1)
    at e.<anonymous> (select2.full.min.js?ver=4.0:1)
    at e.d.invoke (select2.full.min.js?ver=4.0:1)
    at e.d.trigger (select2.full.min.js?ver=4.0:1)
    at e.trigger (select2.full.min.js?ver=4.0:2)
    at select2.full.min.js?ver=4.0:2
    at Object.f.transport.d.status.0.d.status.e.trigger.message (select2.full.min.js?ver=4.0:2)

Cheers,
Tris

Hi Matt,

I gave it a test first thing this morning but unfortunately it seems to it be doing exactly the same thing but with no console error anymore. I definitely downloaded the ‘development version’ as instructed and installed it. I even tried a second time where I uninstalled it and physically deleted the folder on my dev server, downloaded the dev version again and installed it. After testing, I updated Advanced Custom Fields Pro to the new version they seemed to have released over the weekend. Select2 was mentioned as an update log, but no difference to our problem.

Cheers,
Tris

Hi,

I did a little investigation on the edit_input.js file from the Page edit screen; Seems that the jQuery events are not firing. I changed the event trigger from select2:selecting to select2:select and it fired, but the event object data is empty.

$( 'select.fa-select2-field').on( 'select2:select', function( object ) {
			console.dir(object);	
			update_preview( this, object.val );
		});

Output:

n.Event
currentTarget:select#acf-field_59842ca487c10.fa-select2-field.select2-hidden-accessible
data:undefined
delegateTarget:select#acf-field_59842ca487c10.fa-select2-field.select2-hidden-accessible
handleObj:Object
isTrigger:3
jQuery112406977119826624185:true
namespace:""
params:Object
result:undefined
rnamespace:null
target:select#acf-field_59842ca487c10.fa-select2-field.select2-hidden-accessible
timeStamp:1501842805781
type:"select2:select"
__proto__:Object

Cheers,
Tris

I have managed to resolve this. Strange no errors appeared in my debug.log file last thing yesterday. This morning I checked and there were a whole bunch of timeouts. So I updated my php.ini and changing max_execution_time from 30 to 180 (3 minutes). Whilst there you could also set max_input_time. I believe an overall solution is to update your wp-config.php set_time_limit(180).

I am running the Layers Pro v2 plugin with Contact Form 7, since Layers Pro v2 the Customiser is dreadfully slow (over a minute).

Thanks,
Tristan

• This reply was modified 7 years, 4 months ago by tmargot.

On their website is states “WordPress has asked us for some updates to the code of our plugin. We hope to have it back in the Plugin Directory very soon. Our changelog below will be updated accordingly. Thanks.”

https://www.mandsconsulting.com/vendor-solutions/products/wp-email-before-download/

So I assume yes, but it will be back. It is probably linked to the latest WordPress update. It would be nice to know why, if it is related to a security issue and the new WordPress some could be vulnerable.

• This reply was modified 7 years, 5 months ago by tmargot.