skylabb

Thanks for the response. I’m looking forward to version 4.0. Sounds like great stuff is coming.

• This reply was modified 7 years ago by skylabb.

Thanks for the excellent support, Greg. I revised the review one more time, and you earn all my 5 stars!

I found the Default Visibility setting which is what I needed. I initially overlooked this part because the way it’s labeled. Visibility is a very general word that can mean a lot of things. So I thinking re-naming this label as “Post Expiration Time” or something close to this would describe this setting more precisely.

Have a good day.
Steven

• This reply was modified 7 years, 1 month ago by skylabb.

Thanks for the reply, Greg.

Yes, that works and is just what I was looking for. Giving the review one more star for that!

Also, it looks like the default expiration period is 4 weeks. It would be awesome if the admin has the option to set expiration time by number of days or weeks.

I’m integrating this plugin for my project and hope to get good support so we can continue to make this plugin a great one.

Thank you.
Steven

• This reply was modified 7 years, 1 month ago by skylabb.

One vote from me on this feature as well. I can’t find another plugin offering this feature either. This would make this plugin so much more powerful.

Thank you.

Thanks for the quick reply Michael.

I appreciate the free plugins and their author’s contribution. I would think the function of displaying custom posts by category or tag is fairly basic and not a special requirement. I wasn’t aware of that the pay version takes care of this part. You guys gotta each and pay the bills – understandable.

cheers

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

With quick and helpful support, you’ve convinced me to purchase the pro version. It’s looking powerful.

/ Steven

Hi, I have the same problem.

ACF and Jetpack are both essential to run a WP site. So the two being friends is indispensable. Issue track on Github seems to be closed. Though with everything updated to latest version, I’m still getting the error.

Hope this can be resolved soon.

Thank you.

Thanks for the quick reply, Jeff.
Ah, the Pro version has the answer. As you mentioned, this is a pretty basic feature and should be included in the free version.

Furthermore for the pro version (if not included already), it would be more powerful to allow set the form for custom posts as an option if one wants to separate the user data under a custom post area.

cheers

@cinematic

This is 2017. When you review and rate software, you also rate user experience, not just technical consideration. It wasted my time downloading and installing it, figuring out how it works, and only to get the surprise – that’s what’s wrong with it to answer your question.

On the other hand, it looks like the author has finally emphasized the plugin requirement in their description right at the top. So that’s good. I will remove this review as it’s no longer valid.

• This reply was modified 7 years, 11 months ago by skylabb.

@cinematic

Before you’re too quick to make your statement since you thought I was too quick to make my review about this plugin, you may want read my review a bit more carefully.

Advanced Custom Fields Page Builder as it says in the name, requires ACF – that I know and that’s why I tried this plugin. ACF is FREE and the author offers additional commercial plugins that enhance ACF. Advanced Custom Fields Page Builder only states that it requires ACF which is not really the case. It requires Flexible Content, which is a commercial plugin that works with ACF.

So likewise, your response says more about you than about the response.

• This reply was modified 7 years, 11 months ago by skylabb.
• This reply was modified 7 years, 11 months ago by skylabb.

Thanks for further explanation on the issue, Jan. Ditto to all the points you brought up above. The prompting “error” message is very deceiving. And the author is not supposed to be collecting specific user data such as site url and email address in a manner that users think that they would have to provide the info order for the plugin to work.

Thanks a bunch @sirspacey. Server space full caused the same issue for me. After adding more space, problem solved. Happy.