Debugging HTML/CSS is super fun for me. Debugging javascript is a nightmare.

I managed to find the cause of this issue after some digging and researching! Sticky might not work if a parent element is set to overflow: hidden/auto/scroll.

The offender? The content class that the Ptabs plugin is looking for.

If you go into your stylesheet, CTRL/CMD + F for the following line of code:

.container > .content { overflow: hidden; }

Remove it if you want the sticky functionality. Just be warned that users who make the choice of extra wide images or tables will now stretch out past the theme wrapper. This can easily be avoided with rules against it and making sure the img element has an overall max-width (I suggest setting this in the stylesheet instead of relying on a plugin or javascript since those can break links).

I found the issue! Rather, I found the support request about it lol. support.proboards.com/thread/660969/tabbed-section-post-plugin-working

The plugin is looking for the default HTML elements/classes for posts using td. Leap replaced those with divs.

To fix, go to the Layout Templates and replace the entire code blocks in the following:

(Also I'm assuming you're using V2, so anyone looking for this with V1, you can compare the code blocks for what needs to change.)

Threads > Thread Tab
<div class="container posts" style="border:none!important;">
<div class="punishment-titlee">
{if $[reply_button]}
       <a href="$[reply_button.href]"><div>write reply</div></a>
{/if}
<h1>$[thread.subject]</h1>
       <h2></h2>
</div>
<div class="control-bar ui-helper-clearfix $[scroll_class]">
$[search]
<div class="controls">
$[action_menu]
</div>
<div class="float-left">$[thread.icons]</div>
$[pagination]
</div>
<div class="content cap-bottom">
$[thread.labels]
$[poll]
<table class="list" role="presentation">
<tbody class="$[list_class]">
$[post_list]
</tbody>
</table>
{if !$[quick_reply]}{if $[bottom_reply_button]}
<div class="reply_button pad-all-double">$[bottom_reply_button]<br class="clear" /></div>
{/if}{/if}
</div>
</div>
$[quick_reply]

Threads > Post List Tab
{foreach $[post]}
<tr id="$[post.content_id]" class="$[post.content_class]{if $[viewing_recent_posts]} recent{/if}">
<td class="$[post.unblocked_class] content">
<div class="punishment-mini-block">
               $[post.created_by.miniprofile]
           </div>
           <article>
               <div class="punishment-mini-bottom" id="punishment-minn-$[post.created_by.id]">
                   <a href="$[post.thread.link.href]"><div class="punishment-mini-thred">$[post.thread.subject]</div></a>
                   <div class="punishment-mini-thred-1">
                       <div>POSTED ON $[post.created_on]</div>
                       {if $[post.likes.total] >= 1}<div>$[post.likes]</div>{/if}
                   </div>
                   <div class="controls">
                       $[post.quote_button]
                       $[post.edit_button]
                       $[post.likes.button]
                       $[post.select_options]
                   </div>
               </div>
               <h3 class="title aria-hidden">Post by $[post.created_by.name] on $[post.created_on]</h3>
               <div class="punishment-post"><div class="message">$[post.message]</div></div>
           </article>
           {if $[post.edited]}
               <div class="punishment-edit"><div>LAST EDIT: $[post.edited.date] by $[post.edited.by_user]</div></div>
           {/if}
           {if $[post.created_by.signature]}
               <div class="punishment-signature">$[post.created_by.signature]</div>
           {/if}
       </td>
   </tr>
<style>
   #punishment-minn-$[post.created_by.id] .punishment-mini-thred:hover, #punishment-minn-$[post.created_by.id] .button:hover, #punishment-minn-$[post.created_by.id] .liked.likes-button, #punishment-minn-$[post.created_by.id] .punishment-mini-thred-1 a { color:#$[post.created_by.group.color]!important; }
</style>
{/foreach}
{if !$[post]}
No posts were found.
{/if}

🤔 Huh. Then there's definitely something theme-specific interfering, which is a little strange since the post makes it look like the entirety of the plugin isn't even loading.

I'm already off for the night, but if there's no resolution by tomorrow, I'll try debugging again in the morning!

This is the test site for your actual site, correct?

Double-check the version number of the Style Tag plugin on the main site to what you have on the test site.

I'm using version 1.6.4 on my test site because the newer versions of Style Tags (likely due to optimizations done for load time) conflicts with PTabs (which has not been maintained in years).

It has something to do with having styling in the PTab element and how Style Tags grabs everything.

If you don't want to downgrade Style Tags (because it's slower), then remove all styling from PTab elements and override the tab classes within newclass.

I would do something like this (quote because lololol ptab forces its way through the code block):

(removed bc spotify embeds are slow)

You can fix A with this CSS (just slap it at the bottom unless you can find it already in the stylesheet):
.container > .control-bar {
  top: 70px !important;
}

Proboards defaults it to 0px, so any sticky headers will usually cover it up on scroll.

For B, you'll need to update the mini-profile template as well as the CSS, unless you'd rather update it inline with just the template. I'll provide the two-step version.

In your mini-profile template, search for punishment-minn- and update the div it takes you to with class="mini-sticky" (or any class name of choice).

In your CSS, add the following:

.mini-sticky {
position: sticky;
top: 120px;
}

I was only using the inspector for this, but it should work for you!

i'm a professional lurker, but i must break character to gush about my new puppy.

she's soft and wrinkly and a good mix of confident yet submissive (or maybe she's just manipulative lol) and ughhhhhh.

It might help the post the code in question so we can see how you're structuring everything.

If you're customizing b, i, table, tr, td, h1, etc., make sure you have a parent class wrapped around it and style your css as .classname element {}

If you have something set but it's not taking after transferring over, slap !important on it. You never know. xD

Also make sure you are not using any class names that jcink is already using. Your browser dev tools will help with this, or, if you have your own jcink site, look at the stylesheet.

You'll also need to make sure your class names do not conflict with custom themes.

My favorite pass time is annoying my car navigation because I don't want to go on the highway.

John is the one in charge of Jcink.

And this looks like something that started rolling out around mid-October.

For those who can access, support thread 1 & support thread 2.

There's not much that can be done except contacting your ISP (and hoping they permanently fix the issue) or trying a VPN.

Which ISP do you use?

From what I can find, PLDT and Globe recently blocked Jcink, and John thinks it's a false positive flag.

Digimon Cyber Sleuth/Hacker's Memory roleplay, anyone?

Super lax, randomized Digimon starters (+ the ability to choose your own via purchase, + the ability to have up to three 'mon), the opportunity to be a Cyber Body or a Digimon, etc. etc. etc. Pretty much leaving it sandbox outside of the initial application process (& for custom Digimon).

I won't put up any official interest check/staff search, but if you want to help out or are interested, hmu. <3

edit: oh, and it's on jcink.

I started watching I'm Standing on a Million Lives, and it'd honestly be such a neat site concept??

Slice-of-life in some major city yet then everyone gets transported to another world to complete a series of tasks within the time limit before returning. The quest would likely need to be expanded upon as the number of characters grow, perhaps with random teams being assigned to complete a certain task, allowing different characters to rp together each time.

Character classes are randomized with additional classes stacking on top after reaching a certain rank. Revival is a thing unless in a position where they would immediately die again, plus the stakes of "if everyone dies, you actually die," which would likely never happen unless doing a giant boss fight involving the whole site.

Complete the quest and return home like you never left in the first place, only for years to pass in the other world by the time the next quest happens.

I'd be down for it.