61pixels

Hey Craig, thanks. It definitely is a public feed. I was able to get around it as I noticed your “second option” and clicked your other tiny link to get one and that one worked just fine. No idea what happened, or why the button wouldn’t work, but it works again now.

No worries Geoff, I appreciate the response. For this particular client, their IT department went ahead and downgraded to PHP 7.1 at my request and the warnings are gone. Appreciate you guys looking into it though as it may help others in the future.

Appreciate the response. Trust me, I completely know 7.2 is in beta and am not comfortable with it at all. My client’s IT department who set up the server installed it. I had already informed them that it was beta and I would prefer to downgrade it to a version of 7 or 7.1. I was just curious if it was on the roadmap here to update in case they refuse to downgrade.

This works just fine for me. I am using it on 3 sites at the moment, and just installed it on one today and works as expected. Does your theme support dropdowns? Sounds like it’s probably working to me but your theme doesn’t have the CSS necessary for the dropdowns to appear. This plugin does not do anything on the front-end of the site, all it does is add the menu items themselves. You need code in your theme to display them.

@mrwweb no worries at all about 5.0 support, after all it’s not even officially released to the public yet. I’ll get on testing the new version in a few minutes and report back.

Edit:
No console errors at all. Deleted old version, downloaded new, same issues on site (local demo 4.3.8). Tried it on another local site, worked instantly. Went back to first site and thought maybe a caching issue, did a hard refresh CTRL + F5 and boom, now showing up.

For a basic repeater it seems to work perfectly! I will do some more testing with complex Flexible fields and the like and report back, but I’m extremely excited about this! Will look forward to the update for ACF 5.0

@mrwweb Really glad to see you had time to work on this. I just tried it out with the brand new ACF 5 and nothing appears or shows up at all, not even the collapse all button.

I went ahead and tried it on another site with 4.3.8 and the collapse all button shows up, but there is nothing for individual rows? I even did a search through the source code looking for your buton class and nothing is there.

Any thoughts? If we can get it working in 4.3.8 I have no problem downgrading from ACF 5.0 to that to be able to use this.

Just came here for the exact same reason. Updating to latest tosses errors even with WP_debug turned off.

Keesiemeijer thank you so much for that code..

I’ve been googling and struggling with this for two days and NO WHERE did I find a solution. I adjusted your example for my specific instance and this worked like a charm first try. I am in your debt!

Youtag, thank you as well for posting pretty much the EXACT scenario I was having problems with in order to prompt Keesie’s response.

Thanks so much.

No luck ?? Same issues. Tried in FF and IE, also turned on flush and dump..

I went ahead and just migrated the site up the old fashioned way, and am chalking this one up to just some random fluke which will hopefully not happen again. Still wish I could figure out the issue though as it’s driving me nuts as to why only this one site doesn’t work.

Thanks, I actually tried that yesterday as I saw it as a dev version, no luck. I even tried an older version, no luck as well. It really just makes no sense, since every other local site runs just fine.

Running inspector while the package tries to build, I did notice that the second it shows the Build Interrupt message, a JS error does pop up: https://d.pr/i/HxPh no clue what it means or why it happens though. In the temp folder, there are both of the files about half completed it looks like, just it never finishes them off…

Hi Huseyin, I was able to finally figure out the issue. It was an easy fix, I just hadn’t thought of it before.

As you know (and now I do), out of the box your plugin ONLY works with “Posts”. I assumed it would at least work with pages/posts out of the box. In my case I am only using it for pages (I don’t have any posts), therefore it didn’t do anything with the shortcode/function.

I passed in pages as the post_type and now all is well.

Suggestion: I’d update your Installation/Description notes to clearly state this. If I had known from the beginning it would have been a 2 second fix.

Even better, I’d recommend simply updating the settings page for the plugin to have checkboxes for each currently registered post_type and allow users to choose which ones to allow usage for.

Appreciate you looking into it. Notice the deprecated functions are gone, nice!

But unfortunately the shortcode still doesn’t work. Putting the shortcode on a page only outputs the Clear Favorites link. No UL or any of the favorite pages are output.

The widget works correctly and updates (still no AJAX), but so far I’m still having zero luck getting the shortcode to display anything. Even tried it on a brand new install of Twenty Twelve with no other plugins activated.

Memory issues wouldn’t be a problem considering hundreds of my other sites locally on XAMPP all run it just fine. This site is only 30mb total, others I’ve ran locally are 100-200mb+ .

No caching or minifying plugins run either, exact same plugins + setup as my other sites locally. I have a feeling it is one of those fluke one in a million scenarios that we’ll never get to the bottom of ??

Thanks for the response. It’s not any of those issues as this is a localhost on my personal computer. As I mentioned, I can run duplicator on other sites on my local computer just fine, it’s just this site in particular. So it must be something unique that is messed up in the database or a fluke thing.

I ended up giving up and just doing it the old fashioned way by exporting/importing the database manually. But it is still really strange and I hope I don’t run into it again. This is the first time this has ever happened locally after hundreds of successful runs.

Tom, strangely enough that was it! If I move the lines to the start of the file it works just fine. I previously had them at the end of the file. Thanks for looking into it.