Mudplugger

OK, I’ve figured it out and posted a hack here

Hope this helps people out, this is a great little plugin.

In order for Advanced Access Manager to control which user roles can access the Spider Calendar we would need to know what capabilities you have coded into Spider Calendar that allows the Admin to see the menu that other users cannot.

I have been unable to determine which capabilities you are using as there do not seem to be any which clearly relate to spider calendar.

Is it possible that you are using some other method to restrict who can see the calendar menu? Can you tell us how you are doing this so that we could show the menu to all users and then restrict access to it using AAM please?

Thanks

Playing around with the phpmyadmin to get the admin username replaced I’ve also noticed that your plugin doesn’t remove the User ID = 1 concern at the moment. Is this also something that could be included in a future release?

Thanks for the info. I’ve had my hosting plan with the same company for nearly 15 years and it’s always been IIS. Also as it’s a reseller plan I would have to do quite a bit of research into how changing to a LAMP server at this stage would effect my clients.

So food for thought, but I’ll just have to see how I get on with regard to security and if the situation become untenable then I’ll have to start considering a change.

It’s a company here in the UK called eHosting, they do offer a LAMP server setup but I’m currently running IIS 7.5.

This is the first time I’ve used Better WP Security and after reverting back to 3.6.6 as 4.0.2 doesn’t work I thought I would check to see what happens when Away mode is activated for the time period 10pm to 6am.

It seems absolutely nothing. Hasn’t stopped me logging into my backend at all.

That coupled with no acknowledgement of a lot of the posts on this forum today by the developer, it looks like their chances of making money on the pro upgrade are disappearing fast.

Oh well, off to the competition then.

Ok, so I’ve managed to get the following error message from my hosting providers:

PHP Warning: is_readable(): open_basedir restriction in effect. File(C:\Inetpub\vhosts\domain.com\dev/wp-content/plugins/C:\Inetpub\vhosts\domain.com\dev\wp-content\plugins\better-wp-security//lang/it-l10n-better-wp-security-en_US.mo) is not within the allowed path(s): (C:/Inetpub/vhosts/domain.com\;C:\Windows\Temp\) in C:\Inetpub\vhosts\domain.com\dev\wp-includes\l10n.php on line 457

I’ll admit to not being a php developer so feel free to tell me I’m spouting rubbish but isn’t the path:

(C:\Inetpub\vhosts\domain.com\dev/wp-content/plugins/C:\Inetpub\vhosts\domain.com\dev\wp-content\plugins\better-wp-security//lang/it-l10n-better-wp-security-en_US.mo)

constructed wrong?

Mine too. Admittedly I am on a windows server which I know everyone hates but there is no information that says the update doesn’t work on Windows server.

I’m trying to get an error log as I post this so will update when I have more info.

If you are wanting to specify that user A can see user B’s list but cannot see user C’s list then I don’t think this is possible at the moment.

You can change the List View setting to Groups which will allow all users to share a single list but everyone would be able to see all items assigned to all users.

I’m building a site at the moment that uses this plugin quite extensively and I’m eagerly awaiting Cindy’s rewrite to see what new features she is adding.

So I’ve played around with this a bit more while I wait for a reply from you guys. The following all applies to the original subdomain that I mentioned in my first post.

I’ve reinstated the original index.html file that was created by the server processes when setting up the subdomain and that displays perfectly, so it’s definitely and issue between the server and WP rather than just a problem with the server displaying any webpage.

I have created a new database, edited the wp-config file and rerun the install.php script. That allows me to see content that is in the brand new DB rather than the original one using the wp-admin panel but I still get the HTTP 500 error when visiting the page so I guess that rules out a problem with the original DB.

I have renamed the .htaccess file (not that this should be needed as this is a windows server) and the web.config file but that doesn’t resolve the problem. I have done this as neither of those files appear in the second subdomain that I set up and that one works.

Hopefully this rules out a few possibilities and gives you guys some more information so that you might be able to help me.

TIA

OK so I have now tried the following.

Created new subdomain (dev2), new database & new user.

Copied WP3.5.1 to new sub domain and run install script.

This all works fine.

The next bit is guess work on my part just to see if I could narrow down the source of the problem I’m not even sure if this is possible. I tried editing the dev2 subdomain’s wp-config.php file to use the DB info for the dev subdomain and got an HTTP 500 error. I also tried the reverse but that resulted in an HTTP 500 error also. I corrected both wp-config.php files and dev continues to give the error and dev2 continues to work.

So should it be possible swap databases between WP installations just by changing the dbname, username and pwd in the wp-config.php file?

And does the working install in the new subdomain offer any clues to why the original install is not working?

Yes, please see first post.

I’m thinking about setting up a new subdomain tomorrow and doing a full install from scratch just in case something has gone peculiar.

OK,

So I’ve deleted everything as per your instructions and the Detailed Upgrade Guide.

Downloaded WP 3.5.1 again and unzipped it.

Copied 3.5.1 back onto the server using FTP.

Performed a Folder by Folder check that all item counts match to ensure all files have uploaded.

The only files that I have not replaced are .htaccess, wp-config.php, web.config and a couple of items that I guess the server creates when you set up the subdomain.

The only files that are not part of the standard WP install is a Theme called wrings but this is not yet active on the site I have been using the twentyeleven theme before the upgrade.

I can still access the wp-admin panel but I still get the same error when I try to visit the site.

I’ve asked if there are any other error messages and am being told that the ones in my original post are the ones that the hosting company is seeing.