cullaloe

Thank you, Matt and Thom. This works a treat. Will this mod make an appearance in future updates, or am I going to have to remember to re-apply the changes? I hate remembering stuff.

I think I have the same requirements as you do @carsononline. What I have in my .htaccess is:

Deny from all

I have three separate folders within the root/wordpress folder for three sets of files. Each of these folders contains that .htaccess file. Nothing in these folders or their subfolders can be accessed directly through a browser, even if you know the path to the file. All are accessible and downloadable via Thom’s brilliant plugin.

Hope that’s helpful.

I found a new plugin to replace WP-Filebase Pro that is actually a great deal better for my purposes. it’s Thom Stark’s FileAway. I find it provides all of the functionality I needed without the pain of filebase synchronisation which has become problematic and unstable.

Thanks, Fabian, for all of your efforts supporting my site over the past 2 years and I wish you well.

Boom. Thanks, Thom for your super-fast and non-judgemental response to my snotty remarks above – other readers should disregard my remark above, or at least read Thom’s response in context with it. He’s right, it works, and I learned something today.

You can see the public files on my site at https://sptr.net under the resources menu. If you’re not a member, you can’t see the private stuff, which is what I wanted.

Top plugin, top bloke.

You can’t stop the world from accessing your files if they have a direct link, in the same way that robots.txt doesn’t stop crawlers from accessing and indexing your public directories.

As I understand it, this is a very nice plugin but it can’t provide security for your files by denying access to anyone/anybot who has the path. It does a lot, but not that.

Same problem:

Fatal error: Class 'getid3_lib' not found in /SERVERPATH/wp-content/plugins/wp-filebase-pro/classes/GetID3.php on line 52

Other posts here seem to suggest that WP-FILEBASE PRO developer, Fabian Schlieper, has gone missing in action and although he seems able to collect fees for support, he is unable to deliver that support. Anybody know for sure?

This is a serious problem for my site at https://sptr.net.

Here’s what I did to reach a working solution:
In Appearance, Edit CSS, added this…

.site-header .site-branding {
	background-repeat: no-repeat;
	background-size: 100%;
	background-position: left center;
}

It’s not perfect but it keeps the important bit of the header image intact at https://iopscompetition.org.uk/.

HTH.

Hi, I have the same feature on https://iopscompetition.org.uk. It would be nice to lock the image in place…

@dfawatts unzip the file and put the jp-disable-og folder (containing the plugin php file) into your wp-content “plugins” folder. Then visit your admin panel to activate the plugin.

FWIW, I’ve gone for bbPress in the end. A bit clunky but less hassle.

https://sptr.net

Thanks Jeremy – again, to the rescue with this jetPack nonsense. Much appreciated.

https://sptr.net

@jeremy Herve thanks, but I think you’re missing something important here about how wordpress is used. Less than 0.15% of my users community are remotely interested in wordpress, let alone have an account at wordpress.com. They just want the site to work without anything confusing, confusing them. JetPack is confusing because it’s totally irrelevant to them. Users that come across it panic and either give up or email the admin.

I’ll be using the plugin to remove Jetpack from non admins to keep it as not confusing as I can for my poor confused users.

And before you ask, all of my users have at least an honours degree in Physics.

It would have been nice to have been able to opt in/out of the JetPack panel for non-admins.

Best,

Nick Hood
https://sptr.net
https://mrhood.net
https://cullaloe.com
etc..

Thanks for commenting – I’ll give it another try.

No, this is a long time bug in WPMU. It’s been there for years. I think you’re stuck with allowing public registrations.

OK. This is what I did to fix this.

Using php-myAdmin, updated wp_blogs such that the site_id=1 (the main blog).

Then, visited each site and ran the /wp-admin/update.php script. This updated the database version to the current value (in blog_versions, db_version=15260)

Then ran the database repair script /wp_admin/maint/repair.php to check it was all hunky dory.

All the sites *seem* to be working OK now.

Still digging.

The updated blogs which work OK all have db_version 15260, which I guess would be the 3.0 version. The two blogs which do not work are (a) located in the root directory and (b) have db_version 12329.

Is there a script I can run manually to upgrade these two sites?

Thanks.

Nick