TPDBrendan

Worked perfectly, thanks!

I’m having the same issue with it stopping at exactly 25 posts, but I’m using it without any particular arguments – just calling all posts. The blog I’m working on has over 450 posts, so I wonder if it’s related to size of database call.

If I use the button option instead of the infinite scroll, I can still load more by manually clicking the button after each load past the first 25. That gets pretty tedious after a while, though, since it only seems to load a few at a time.

• This reply was modified 8 years, 4 months ago by TPDBrendan. Reason: forgot some info

I heard back from Swiftype and they shared this gist., which has worked like a charm for me. Hope it helps you out!

I have the same exact problem on the project I’m working on now. I have a custom post type ‘members’ with two custom taxonomies – ‘specialties’, which is hierarchical, and ‘tags’, which is not.

Unfortunately, the code offered here only works for standard categories, not custom taxonomies. I tried altering it by using get_terms, but I get errors even just trying to use it for standard categories.

Waiting to hear back from Swiftype on a request I made to the linked article above.

I’m having an odd experience, the new version exports the .wpress file just fine, but the import function just don’t work at all. The dropdown menu doesn’t work and when I drag and drop the exported .wpress into the import box the browser just redownloads the file itself again. It doesn’t show any error dialog boxes, it just downloads the file again.

I’m using it on a wordpress installation hosted locally on MAMP and I’ve tried it in both Firefox and Chrome, if that helps at all. Love the plugin otherwise, but without import it’s kinda pointless.

Nevermind, just purchased the pro version and I had the same problem. Now that I have paid for the pro version is there any way that I can get some more specific support on this issue? It’s pretty critical for the project I’m working on right now for the client to see the site in progress.

Could this have to do with the fact that I’m using the free verson? I just noticed in the FAQ that it says only the pro version has multisite support. I didn’t realize that and since it was working on my subdirectory sites I assumed it must be a bug.

Yea, they’re on the same domain for front and back-end. I’ve tried clearing the browser cache as well, but same issue.

My multi-site network is set up using subdirectories and the plugin works for any of the subdirectory sites, but doesn’t seem to work for the primary domain. I’ve tried logging out and only logging in through the primary domain, but I still see the coming soon screen. To reiterate, I’m not using domain mapping, just the default subdirectory set up.

I’m having the same exact issue – logged into the primary domain of my multisite and still seeing the coming soon page on the frontend. It removes the black WP bar at the top as well, so it seems to really think I’m logged out.

I have two other sites on my network that are not using the coming soon page. If I navigate over to them, the black WP admin bar returns to the top of the frontend. So, it must be an issue with the plugin having difficulty recognizing login status on sites that it is active.