Douglas Bell

Here is modified CSS (mostly the same as bdbrown’s with a few tweaks:

/* compress progressbar to make room for timers */
.jp-progress-container {
  margin-left: 65px;
  margin-right: 120px;
}
.jp-progress-container,
.jp-volume-bar-container {
	border-left: 0;
}
/* move timers up and left */
.jp-duration {
  margin-top: -15px;
  margin-left: -65px;
}
.jp-current-time {
  margin-top: -15px;
  margin-left: -42px;
  width: 44px;
}
/* fonts for timers */
.jp-current-time, .jp-duration {
  color: #fff;
  font-size: 12px;
}

And of course since I’m using a child theme, here is the entirety of inc/post-formats.php that I put in my child theme. The only section that I’ve modified is the audio post format, since that’s the only one I use on my site regularly.

https://pastebin.com/kz0tQdtw

One modification that I made from bdbrown’s code was a slightly different view for mobile browsers. In my testing, mobile web browsers were rendering the player differently, in that they were not displaying the volume slider (which, admittedly, is a bit too small for a touch interface anyway), so as a quick hack, I use wp_is_mobile() to remove the volume slider and alter the layout of the remaining elements.

Sorry for the late response (I got a bit busy with other projects over the past month or two). I just set up this code and it looks perfect… thank you very much for the help.

I made a few additional tweaks on the backend for layout (like removing the left-borders from .jp-progress-container and .jp-volume-bar-container since they were clashing with the counter text), and also made some adjustments for display on mobile devices.

I really appreciate you taking the time to help me out with some code… thanks again!

Here’s a full paste of inc/post-formats.php from the Hueman theme… I’m trying to add that jp-current-time div somewhere around lines 59/60/61.

https://pastebin.com/3AzPDrHa

Most likely what needs to happen is that I need to add in the jp-current-time div there and then make edits to the jPlayer classes defined in style.css (lines 1027-1072) in order to resize the other elements to make room for the elapsed time counter.

Hi bdbrown,

The site is https://krpoliticaljunkie.com

Because it’s a live site, I can’t keep the elapsed time visible for you to see directly… I’m only able to tinker with this while I have the site in maintenance mode. However I’ve taken some screenshots of what it looks like.

In <b>inc/post-formats.php</b> if I add <div class="jp-current-time"></div> AFTER the </ul> on line 59 but BEFORE the <div class="jp-progress-container"> on line 60, I get this: https://krpoliticaljunkie.com/temp/jplayer-elapsed-1.jpg

But if I add the jp-current-time div AFTER <div class="jp-progress-container"> on line 60 but BEFORE <div class="jp-progress"> on line 61, I get this: https://krpoliticaljunkie.com/temp/jplayer-elapsed-2.jpg

And if I add the jp-current-time div anywhere within the “jp-progress” div (after line 61), then the player layout looks normal (with the elapsed time not visible), but the seek bar doesn’t show any change nor does it respond to mouse clicks during playback.

(And of course, I’m using a child theme, so once I can figure out how to make this work I will make sure to roll back any direct code changes in inc/post-formats.php and do them through the child theme.)

Thanks for your assistance!

Although I’m not dead personally, I haven’t had a chance to get very far along on this, and I’m really sorry about that. I’m on my winter break now so I might try to make an effort to get back to this little plugin in the next week or two, but I don’t want to make any promises at this point.

I had this happen too, but the problem is fairly easy to fix.

The reason that WordPress can’t find wp-content/plugins/jw-player-plugin-for-wordpress/skins/newtube/newtube.zip is because the folder is actually named NewTube, not newtube. All you have to do is go into that skins directory and fix the capitalization of that particular folder’s name.

Hopefully LTV will fix that in an update.

Interestingly enough, this plugin originated from code that I had previously written for a PTA website. Funny how that works out!

My current plans for version 2.0 include writing this plugin to utilize some of the WordPress infrastructures for managing data, which should allow for bios, pictures, and other custom fields to be defined for officers, and even provide them with their own directory page. Thanks for the suggestions.

You’ll probably want to code this yourself. You can use WordPress’ Plugin API to create a function that does all of these things, then use the following action hook to register your function:
add_action('wpmu_new_blog', 'your_function_here');

With that, WordPress will execute the function your_function_here() whenever a new site is created. The your_function_here() function should accept one argument, which is the ID number of the blog that was just created.

I would also recommend placing that plugin instead of the wp-content/mu-plugins/ directory (you have to create that directory yourself, it’s not there by default), which will automatically ensure that your plugin is executed on all sites.

When you first set up WordPress Multi-Site, you have to choose between subdomains or subdirectories. Once you make that choice, and your network is set up, you are permanently stuck with that setting.

If you want to use subdirectories instead, you will need to remove your current installation and set it up again from scratch. Be sure you set up your Network immediately after installing WordPress 3.0; once you start creating content on your main site blog, WordPress doesn’t let you use a “subdirectories” set up anymore.

For plugins and themes, you’re going to have to download those from your old site and move them to the new site manually.

For everything else, you can use WordPress’ built-in Export function — just go to the Tools menu and choose Export. (I recommend that if you have a lot of spam comments in your Akismet spam queue, you delete them before doing this.) Then on the other install, go to Import under the Tools menu, and click on WordPress. WP will prompt you to install a “WordPress Export File” plugin, and once you’ve done that, you can use that tool to upload the file that you exported previously.

That should work unless you have a enormous amount of content to move over. In that case, you can also do a full export of your WordPress database tables from within phpMyAdmin, and then import them to the other site also using phpMyAdmin.

“Facebook Like” Plugins

Pick whichever one you like. (Pun intended.)

New users are already automatically added as subscribers to one of your sites, which you specify in your Network Options page (listed as Options under the Super Admin menu in your admin). However all of those users already have permissions equivalent to subscribers on all of the other sites, even though they aren’t necessarily listed as such. (In short, they can view sites, leave comments on sites, and edit their own profile.)

I don’t off the top of my head know of a plugin that allows users to be auto-assigned permissions across the entire network, but if you simply want to assign Subscriber permissions to everyone, it’s not entirely necessary to do so, since it doesn’t give them any more privileges than they already have.

I’ll get to the easier part: WordPress Multi-Site doesn’t require a VPS unless you’re intending to scale it for hundreds or thousands of blogs. It’s just like any other website–the more stuff you have on it, the more it’s going to eat up your bandwidth, execute lots of queries to the database, etc. The point when you’re starting to hog too much resources from the shared server is the point when you’d need a VPS.

However I use WP Multi-Site on a shared hosting account with no problems, considering that I’m only running a few dozen small blogs on my network. However if you’re going to run WordPress multi-site with subdomains (blog.example.com), you’re going to need to make sure that your host will let your create a “virtual subdomain.” In cPanel, this is the equivalent of creating a subdomain *.example.com and having it direct to the root of your hosting account. Not all shared hosts allow this specifically because they’re scared of the possible weight of WP Multi-Site, but a number should allow it just fine.

You might consider BuddyPress (www.buddypress.org) which integrates a wide variety of social features–including a bbPress forum–in with WordPress (in both the standalone and multi-site flavors).

Did you update your .htaccess file upon setting up the multi-site installation? That’s the most likely cause of your 404.

Just to confirm, are you using subdirectories (example.com/blog/) or subdomains (blog.example.com)? Both of them are “multi-site,” just different ways of implementing it.

Unfortunately, the visual editor setting is set on a site-by-site basis within a multi-site network, there is no way to make that change globally without using some sort of plugin.

But you know, even if you leave the WYSIWYG on, there is a tab that appears above the content area that says “HTML” — just click that and you’ll have the same plaintext editor that you know and love. I’d recommend just doing that, it saves you the trip to your user options on all those sites just to uncheck that checkbox.