Support

Account

Register Login

Forum Replies Created

  • Brian,

    I guess this is out side the scope of ACF. However, one strategy (that might work) could be:

    1. Hide your images with css:
    #gallery-1 { display:none;}

    2. Create a button “Photos”

    3. Add a jQuery click event listener to the button that performs/fakes a “Click” on the first image – to start the Simple Lightbox:

    jQuery(document).ready(function($) {
	// cache variables -Id #btn-photos is generic - chang with your own actual ID or Class
	var btnPhotos = $("#btn-photos"),
		galleryItems = $("#gallery-1").find(".gallery-item a");

	$("#btn-photos").click(function(event) {
		// something like this MIGHT work..
		galleryItems.first().click();
	});
});

    Might be better ways, but this is first that came to mind.

    Regards!

  • We are using default settings for WYSIWYG

    We have not set any custom caps, however we are using Woocommerce – which does, i think.

    If you have problems recreating the issue – this was my case also. Other admin users of the site reported the problem, but my user did not have any issues – so I did not believe them … until I created a new admin user and logged in as that guy – then I saw that they where telling the truth..

    Now after using CCleaner to clear everything – my user is also gets the error.

    1. we have a repeater field that has a post obj field as a sub field.
    2. we have tested it with Woocommerce’s ‘products’ as post object.
    3. we have tested it with a personal created CTP called Deals as post object.
    4. Happened on the woo single product
    5. happened on another single CTP as well (when testing if this was woo related)
    6. Problem does not occur when repeater field is disabled..

    Possible workaround is to use relationship field instead of repeater field.

  • Elliot,

    Thanks for getting on this 🙂

    Same line as hedgehog:

    ReferenceError: reference to undefined property this._frameWidth
    http://***/wp-content/plugins/advanced-custom-fields/js/input.js?ver=4.3.0
    Line 339

  • We managed to get our client’s site working again by

    1. changing the the repeater field containing a post object to a relationship field instead.

    Hope this gives a hint to others with the same problem

  • We can verify that this is the issue!

    This happens when a repeater field includes a post object field.

    (We also see that in the case where repeater has a post object the memory load on the server goes to the sky, and in some cases it breaks the limit:

    Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 71 bytes) in /var/www/alwaysfootball.dk/public_html/wp-includes/meta.php on line 578

    This could be related – but not verified)

  • Elliot,

    The post object field is pretty basic and will load in a lot of data when repeated many times…

    No, this is not the issue.

    this is the issue:

    I’ve narrowed the problem down further. The problem only occurs when I add a “post object” field into the 2nd-level repeater field. If I change the post object field to a text field, everything works. Weird…

    +1 to solve this issue…

  • +1 to solve this issue!

  • This issue is not solved..

    Elliot,

    the problem happened after we cloned the site to another server.

    1. first it was existent only for some users -my admin user was working. This explains why, in other threads on the topic, there was a note that the developers could not recreate the problem.

    2. now, after I have cleared my browser cache – my user also have this – wp is not defined javascript error

    3. error from firebug console is:

    ReferenceError: wp is not defined
    http://alwaysfootball.dk/wp-content/plugins/advanced-custom-fields/js/input.min.js?ver=4.3.0
    Line 13

    4. Disabling plugins showed that the only plugin on the site that generated this error was Advanced Custom Fields: Repeater Field.

    However, we rely very much on this plugin so disabling it is not an option..

    5. We have updated to the ACF master described in this post – and the error is still there..

    We really hope that you can put high priority on this issue as this product is no longer working.

    Best Regards,
    BK

Viewing 8 posts - 1 through 8 (of 8 total)