All posts by Andrewds1021

@Headquarter8302 Do either of those work on a mobile device?

Okay. After taking a closer look. I think I figured it out. First, be sure to delete the previous suggestion if you haven't already. Then add this.

.mw-parser-output .wds-tabber {
    overflow: visible;
}

Roles should be given out as needed to those who are trustworthy and deserve it. A wiki that small probably doesn't even need more than 1 admin; never mind more than 1 bureaucrat.

Posting this question again (see here and here) is not likely to get you a different answer.

I don't think there are any bot programs for mobile, are there? Also, the point of the achievement is to recognize those who put effort into the wiki; presumably by contributing every day. Using a bot to do that sort of defeats the purpose and could be considered edit farming.

The particular image you posted in the opening post of the thread you linked to is about 1.5 MB, If it really took 10 minutes to upload, there is probably either an issue with your internet connection or Fandom's servers. However, while the maximum size is 10 MB, usually images around 5 MB start causing loading issues. As such, I would suggest not going much larger than 2 MB just to be safe.

I know you already fixed the issue but it was probably due to a box-shadow. I currently do a similar thing on Oasis and sometimes I get a "transparent phantom" due to the local wiki's CSS.

Unless you are going to put the text in the same tab as the image, you can't do that. You are not doing the same thing the other wiki is so you cannot get the exact same appearance.

That is because they used Template:Infobox_CVG instead of Template:Infobox_CVOG. It is not a mistake; they used a different template. From what I can tell, the template they used is a remake of the one you are using and uses the new portable infobox format. You might want to consider changing to that instead.

I believe this thread might be of some use.

Well, it doesn't seem to be working on Oasis either so I am curious if it was re-disabled or if SlyCooperFan1's information was mistaken.

The bottom line is that the pages that showed that stuff are all still there. It is just that the new layout doesn't provide as many convenient links to those pages. On the old skin, the links for recently added videos, recently added images, and recent changes were all available in both the Explore navigation menu as well as the icons in the top-right. However, on the new skin, only recent changes is available and only in the top-right icons.

That said, keep in mind the the page for recent videos and recent images is actually the same page. Also, you can easily switch between the page for recent videos/images and the page for recent changes using the tabs under the page titles on those pages; the ones that read "Wiki Activity", "Social Activity", "Image Activity".

Are you talking about text such as "Welcome to the r/Teenagers Minecraft Server Wiki!"? That appears centered in both layouts for me. As for the gallery captions, if you want all gallery captions on all pages to be centered, you can add this CSS.

ul.gallery li.gallerybox div.gallerytext {
    text-align: center;
}

When you submit a ticket to Fandom, it can take several business days (i.e. not Saturady, Sunday, or holidays) to get a response. So it is not surprising that the account has not been given bot status after just a few hours.

Short Answer:

With the move to UCP, only the Popular Pages rail module exists for regular users to see "most visited pages". Admins can additionally access Special:Analytics which shows the top 10. However, with the new layout, Popular Pages has been removed as well. As such, there is currently no means for non-admins to see "most visited pages". There is the Trending section on category pages but that is only for pages in that specific category.

If I recall correctly, this is related to syntax highlighting. If you disable syntax highlighting, the issue should go away. That said, it is true that it is a bug and Fandom is working on fixing it.

In the example you linked to, both the image and the content change when the user selects a tab. The reason the content is able to float next to the image is that they are both in the same tab. However, in your case, they are not. The images are in the tabs and the content is below the tabs. Because of the way tabs are done, content doesn't float next to it.

You can use a wrapper and site CSS to get the effect you want. Here is an example of what you would put on the page.

<div class="floatright">
<tabber>
<!-- images here -->
</tabber>
</div>

Then, you could add this to the wiki's CSS.

.floatright {
    float: right;
}

Edit: That said, does it need to be tabs? Would a slideshow be sufficient?

How do you sign-in to your main account? Do you use a connected account or do you use a local password?

Sounds like a juicy story.

Is there a workaround while we wait for a fix?