Forum Replies Created

Viewing 15 replies - 136 through 150 (of 154 total)
  • Thread Starter bward

    (@bward)

    Perfect. I tested it to confirm your fix as well for a real-life example. I will certainly leave you a review Jonathan. Thank you sir.

    Thread Starter bward

    (@bward)

    Jonathan,

    Outstanding!

    I started the process of testing yesterday. The updated 2.3.4 code seems to have fixed the issue so thank you very much.

    I will keep an eye out for the conditional drop downs. I see some posts on that and know it is in the works.

    Quick FYI on the shortcode addition (great idea). It seems to display in the head section of a post, rather than where you place the code. I placed the code between the two phrases, “This is a test page”. Here is an example if it helps you, https://585.3cf.myftpupload.com/test-page . When you update a post it does not take you right back to the editor, but tries to load the filter without css.

    Not an issue for me right now, but you may want to know.

    Have a great day and thanks so much for all of your hard work!

    • This reply was modified 6 years, 8 months ago by bward.
    Thread Starter bward

    (@bward)

    Jonathan, this is such an exciting update for us. I really look forward to testing it out. We are close to launching some new things on our site and it would be outstanding if your filter could help sort our content for our readers.

    Thank you so much for taking the time to listen to all of the feedback the community has on your plugin.

    Thread Starter bward

    (@bward)

    Thanks Jonathan.

    Yeah, I tried what you mentioned, but that obviously changes the slug for the post name as well which defeats the purpose of a CPT for us.

    I notice when I change the “has_archive” value, BTF changes the value of the custom post type under “Activate for these post types:“.

    For example mine is:

    “Commentary https://585.3cf.myftpupload.com/commentary/archived”.

    If I change my CPT “has_archive” to “/commentary/test“, BTF would reflect that as well.

    Are there any checkboxes that could be added where BTF would only archive on the “has_archive” value? *hint, hint, nudge, nudge*

    I feel I am so close, but so far away on this one! Thanks sir.

    Thread Starter bward

    (@bward)

    No worries, it happens.

    Yes, that does change it. However, with the plugin disabled it works fine. Meaning, “/commentary” loads the static page that I created and “/commentary/archived” loads the archive for the CPT.

    The only time that stops working is with the plugin turned on. I am hoping there is another way around this, my CPT technically does not have a slug. “/commentary” is nothing, if I remove my static page of “/commentary” then “/commentary” would 404.

    It seems to me the rewrite rules are taking anything in the string (/commentary/archived) and treating it as an archive instead of following the code of:

    “‘has_archive’ => ‘commentary/archived’,”

    • This reply was modified 6 years, 9 months ago by bward.
    • This reply was modified 6 years, 9 months ago by bward.
    • This reply was modified 6 years, 9 months ago by bward.
    Thread Starter bward

    (@bward)

    I am hoping to receive some assistance with this issue. Did I outline the issue clearly enough?

    Thread Starter bward

    (@bward)

    Alright, I appreciate you letting me know. I read that article over.

    Thread Starter bward

    (@bward)

    FYI: I believe it was WordPress using its internal coding to redirect the links it can figure out.

    Thank you for a fantastic plugin!

    Thread Starter bward

    (@bward)

    I see. For our setup we have to share the custom taxonomy with our CPTs, at least most of them. Good to know I was not losing my mind! If you can swing an update at some point I’m sure many would appreciate an already great plugin.

    Thread Starter bward

    (@bward)

    Appreciate the help. I will play around with this. Thank you.

    Thread Starter bward

    (@bward)

    Anders, appreciate the reply sir and you nailed it. Thank you very much!

    Thread Starter bward

    (@bward)

    @jonathandejong I changed it up on you, sorry about that, but I certainly appreciate the response!

    I did have a third drop down on that page, but ended up combining it into the drop-down labeled “Resources”. After looking over this again, I do not see the issue anymore… I wonder if I had caused my own issue and fixed it when I combined one of the menus?

    I do have multiple custom taxonomies, so CPT 1 and CPT 2, both have Tax 1 and Tax 2 assigned to them for use, though they may not specifically be in use by a post.

    Example of the issue I did have.

    CPT 1:
    Tax-1

    CPT 2:
    Tax-1, Tax-2

    On the filter of the archive for CPT 1. I would see Tax-2 as an option, which is not valid since it was not assigned to a post with CPT 1. If I selected that (Tax 2) filter value and selected “apply filter” I would get a broken page as CPT 1 does not have Tax 2 assigned. However, if I selected “Enable conditional dropdown values” I did not have this issue. Though I still saw “Tax-2” even though CPT 1 does not have a Tax 2 value.

    It was a bit confusing from a user level perspective. Again, since I removed that third drop down menu, I do not see this anymore and it functions how I expect.

    If you cannot shed any light on that, no worries, I just do not want to have issues at a later date when we roll this out.

    Thanks so much!

    Thread Starter bward

    (@bward)

    I had to used the “developer” feature on my browser to do a stare and compare with my working archive pages and non-working archive pages. By non-working that means the pages that did not have the HR gray bar separating my posts.

    This is what I found on my working archive pages:

    
    class="post-49822 post type-post status-publish format-standard
    

    Note the “post type-post”.

    Now here is a clip from my new archive which is based on a custom post type.

    
    class="post-49827 bible-study type-bible-study status-publish hentry
    

    Note the “bible-study type-bible-study”.

    I found within my css file the following:

    
    .post, 
    .page { 
    	padding-bottom: 10%; 
    	border-bottom: 4px solid 
    
    #EEE;
    	margin-bottom: 10%;
    }
    

    Since my custom post type is not a “post”, but a custom post type labeled “bible-study” my Bible Study posts were not picking up the css class. So I changed my css to this:

    
    .post,
    .bible-study,
    .page { 
    	padding-bottom: 10%; 
    	border-bottom: 4px solid 
    
    #EEE;
    	margin-bottom: 10%;
    }
    

    Now it works fine. If you have a similar issue, though your theme may vary check here.

    • This reply was modified 6 years, 11 months ago by bward.
    • This reply was modified 6 years, 11 months ago by Jan Dembowski. Reason: Fixed formatting, blockquote doesn't really work
    Thread Starter bward

    (@bward)

    I figured this one out so no one tries to help. Will post how later for reference.

    Thread Starter bward

    (@bward)

    Makes sense, thank you for the reply.

Viewing 15 replies - 136 through 150 (of 154 total)