block

I figured out that if I turn off the “Users must be registered and logged in to comment” setting, the JetPack comments works. However, I don’t want people to be able to leave comments unless they are logged in.

Andrew, thanks for the reply to my question and for the link. In my PayPal settings, I do have the “PayPal Account Optional” setting set to “on”. However, the description for the setting states that the PayPal Account Optional setting does not work for subscription buttons. I am using Paid Memberships Pro for a membership site that requires a monthly payment. Do you know if there is another way to use PMP plugin with PayPal and be able to give users the option to pay by credit card for a subscription? If not, would it work with Stripe?

@dcavins, I added the issue to github as you requested. Also, I added an issue about an error message/warning that appears when trying to save a doc after a taxonomy has been selected. I think the doc still saves, but the error message appears and doesn’t go away until I manually tell the browser to go back.

@fionas, With reference to printing to PDF, on my site I am using the TinyMCE Advanced plugin to enhance the visual editor. In the settings of the plugin, there is a printer button that can be dragged to the editor toolbar to enable it. After that, whenever a user is either creating or editing a doc, he or she can select the printer button (or go to the editor menu File >> Printer to print just the document. Even without the printer button enabled, when creating the original doc, a user can right-click in the doc area and select print to print just the doc. That doesn’t solve the problem for the reader, but perhaps it does provide a PDF for the author.

David,

Thanks for the quick work. The terms are now showing up as check boxes. That works great for my stages of writing taxonomy. However, for genres and subgenres, a stack of checkboxes is going to get long. Is it possible to have a multiselect dropdown, or at least to keep the checkboxes in a hierarchical alphabetical order? By that I mean that the child terms appear under the parent terms (and indented a bit) rather than all terms appearing in alphabetical order. I have a term and a child term that are both the same, so right now they appear one above the other in the stack of alphabetically arranged checkboxes, and the user won’t know to which parent the child belongs. I hope what I am asking for makes sense.

David,

Thank you for creating that plugin! I appreciate it. I used the Custom Post Type UI to create two new taxonomies, then added instances of the taxonomies. (I don’t know what to call the instances. For example, I created Genres as a taxonomy and added Fantasy, Action, etc as the instances). I associated the two new custom taxonomies and also the Categories taxonomy to BP Docs from the Docs >> Taxonomies page. Now, on the Create Doc page, there is a row for each of those taxonomies. However, there is no way to select any instance of the new taxonomies, and for the Categories type, only “uncategorized” appears as an option although other categories exist. What needs to be done next so that the options will appear on the Create Docs page? Is that something you will be working on soon? Is that where the “templates/docs/single/edit.php” file still needs to be edited?

David,

Thank you for the links and for the code. I was able to make it work!

Great. Thanks, David.

Hi, Dave. Thanks for that link. The referenced code is for giving create capabilities to only admins. Can it be modified to work for a non-admin who has a certain membership level? I know enough to add code to a file and follow along a bit, but I don’t know all my wordpress coding lingo.

Dave, thanks for the link to the filter. Does the function end on line 603? Could you tell me what change I need to make to set the default for viewing a doc to logged-in users only? When I update the plugin, will I need to update the code as well in order to maintain that setting?

Hey, @webcrowd. What’s your classifieds website?

Angelleye, somehow the site started working again. It is running PHP 5.2.17 so I’ll have to check with my host about upgrading that. Otherwise, I guess don’t worry about this for now. Thanks.

Nevermind. It does work. I needed to add “https://” before the URL. Consider the ticket resolved.

Okay. I think I got it. Thanks for the help.

Danieliser, thanks for the response and the plugin.