Question greeting notice vanishes on mobile style after installation

[zfx]

Just installed vBNavTabs on my vB 4.2 test site and noticed that it somehow keeps the guest greeting message from displaying on the mobile style for users who are not logged in. The message however still displays normally in full site mode. So is that greeting message (with text from notice_1_html) somehow tied in with the nav templates affecting the mobile style?

 

[Fillip H.]

Does it work on a default (unmodified) skin?

 

[zfx]

Does it work on a default (unmodified) skin?

No, it does not. And when I view the page source, the navbar template code is not even there. BTW, this is on my test site. Conversely, when I view the page source for the mobile style on my live site, the navbar code is in fact present. The difference, of course, is that vBNavTabs is only installed on my test site. The tabs and their options seem to work wonderfully, but the mobile style has no navbar features while vBNavTabs is installed.

 

[zfx]

Update:
While this issue should not have occurred in the first place, and with the understanding that I don't know why it happened but that I very much like and intend to use the vBNavTabs plugin, I have decided to build a simple workaround into the mobile style using a conditional that will force the greeting notice to appear whenever it should be there. To make that happen, I added the following to the mobile style's FORUMHOME template on my test site and so far it seems to work well:

<!-- guest welcome message -->
<vb:if condition="$bbuserinfo['userid'] == 0">

<div data-role="content">    

            <div class="ui-body ui-body-e">If you have not already done so, please create a member account by visiting the member registration form at: <a href="register.php{sessionurl_q}" target="_blank"><b>New Member Registration</b></a>. This website is not publicly accessible ... (and whatever else I would like to add here.)</div>
    
</div>
    </vb:if>
<!-- / guest welcome message -->

In any case, while this works for now, if you ever determine what causes the issue please let me know.

Thank you

 

[DragonByte Technologies]

Hello @zfx,

We hope your ticket regarding vBNavTabs has been addressed to your satisfaction. This ticket has now been scheduled to be closed.

If your ticket has not been resolved, you can reply to this thread at any point in the next 7 days in order to reopen the ticket, afterwards this thread will be closed.

Please do not reply to this thread if your ticket has been resolved.

Thank you.


- DragonByte Technologies, Ltd.

 

[zfx]

I would still like to understand why this happened. Is it a bug perhaps? Have you tried to reproduce it in a test scenario with vB 4.2?

Thanks

 

[Fillip H.]

I don't believe this product is designed to work with vBulletin 4.2's mobile style, so it wouldn't be considered a bug, no.

 

[zfx]

I don't believe this product is designed to work with vBulletin 4.2's mobile style, so it wouldn't be considered a bug, no.

Understood. However, this product does purport to be compatible with vB 4.2. That said, vB 4.2 came with the mobile style, so by my thinking your plugin shouldn't break that style's basic functionality. But I do understand how there can be unintended, uncaught effects with certain plugins. I was mainly hoping to learn whether you could duplicate the failure and, if so, whether you'd have any thoughts on why the failure might be occurring? I believe Ozzy may have worked on this plugin's development. But I'm unsure if he's even still around.

Thanks

 

[Fillip H.]

Sorry, I wasn't very clear: What I meant to say was that the mobile style in vBulletin 4.2 is not really fit for purpose; it doesn't work with any add-on (at least not intentionally, without explicit support being added) and today's web focuses on Responsive design rather than a mobile-specific style.
("Responsive design" means a style that adjusts itself based on the user's viewport, while maintaining the vast majority of functionality. This site uses responsive design.)

For that reason, the mobile style was not very popular. For evidence of this, you need look no further than the fact that no-one else has reported this issue (to my knowledge / recollection), in spite of the hundreds (if not thousands) of users that have used this product.

As far as I can remember, the only add-on that had explicit support for the mobile style was the Advanced User Tagging product for vBulletin 4. This received special attention because without said support, posts would not render correctly on the mobile style.

When you consider the fact that the mobile style is hardly ever used, and the fact that it would take significant time & resources to add support for it, there are no plans to add support for the mobile style to this or any other vBulletin product at this time.

 

[zfx]

Sorry, I wasn't very clear: What I meant to say was that the mobile style in vBulletin 4.2 is not really fit for purpose; it doesn't work with any add-on (at least not intentionally, without explicit support being added) and today's web focuses on Responsive design rather than a mobile-specific style.
("Responsive design" means a style that adjusts itself based on the user's viewport, while maintaining the vast majority of functionality. This site uses responsive design.)

For that reason, the mobile style was not very popular. For evidence of this, you need look no further than the fact that no-one else has reported this issue (to my knowledge / recollection), in spite of the hundreds (if not thousands) of users that have used this product.

As far as I can remember, the only add-on that had explicit support for the mobile style was the Advanced User Tagging product for vBulletin 4. This received special attention because without said support, posts would not render correctly on the mobile style.

When you consider the fact that the mobile style is hardly ever used, and the fact that it would take significant time & resources to add support for it, there are no plans to add support for the mobile style to this or any other vBulletin product at this time.

I understand. But along that premise, I would say that these days the entirety of the vB 4.2 generation of products is questionable as far as being fit for purpose. Absolutely none of the vB 4.x or 3.x products were built around the responsive design concept. Sure, you can make the components somewhat more responsive by utilizing 100% width directives, etc. But let's face it, vB 4.x is outdated technology. Unfortunately, however, that doesn't negate the fact that plenty of vB 3.x and 4.x (v4.2 included) forum sites are still active on the web. Although vB 4.2 will never be ideal, it can be made to be tolerable (to a point at least) by employing an adequate implementation of modifications and fixes here and there. And the same goes for its mobile style.

I was merely asking for confirmation of the issue I reported and for some possible feedback as to which component of the vBNavTabs plugin might be involved. That's all.

Thanks

 

[DragonByte Technologies]

Hello @zfx,

We hope your ticket regarding vBNavTabs has been addressed to your satisfaction. This ticket has now been scheduled to be closed.

If your ticket has not been resolved, you can reply to this thread at any point in the next 7 days in order to reopen the ticket, afterwards this thread will be closed.

Please do not reply to this thread if your ticket has been resolved.

Thank you.


- DragonByte Technologies, Ltd.

 

[DragonByte Technologies]

Hello @zfx,

As we have not heard back from you, your ticket regarding vBNavTabs has now been closed.

If your ticket has not been resolved, please feel free to start a new support ticket and link back to this ticket.

Thank you.


- DragonByte Technologies, Ltd.