Forum Replies Created

Viewing 3 replies - 1 through 3 (of 3 total)
  • Had this same problem folks, alas, we use the podcasting plugin quite a lot, and some other plugins too – does anyone know if the issue is limited to just the podcast plugin?

    best wishes

    Steve Nisbet

    Oddly enough there are a large number of plugins which are targeted at allowing you to execute PHP directly in Posts and Pages, two I have tried in the last week are:

    Both look excellent, both no longer work. They must have worked pre 2.5.1, but some change or other has been committed in 2.5.1 which essentially eradicates or messes with the embeded PHP you put in the post even with the plugins turned on. Indeed, the support forum for Exec-PHP seems to suggest a number of people are having problems specific to 2.1.5

    Annoying

    Howdy,
    I had a similar problem and hunted around plugins for some time trying to find one that would allow access from a range – the nearest plugin was actually aimed at preventing certain IP addresses from accessing the same material.

    The solution in the end took me to add config lines to the Apache Virtual Host container for the site of my blog. The reason you need to use Location is that the request your browser will make is likely to be to a permalink – which has no physical presence on the box, and therefore will not be trapped by a <Directory> directive.

    So, I don’t think you can use Location directives in .htaccess files for the simple reason that htaccess files are used to handle control over physical parts of the tree.

    If you have access to the virtual host config you could put something like this in:

    <Location /private>
    Order Deny,Allow
    Deny from all
    Allow from 234.123 181.45.7.8
    </Location>

    Similarly you could protect a location by any normal Auth method – :- htpasswd, Auth_ldap – and so on.

    Its not elegant, but I didn’t have the time to write something similar in a plugin. Maybe soon!

Viewing 3 replies - 1 through 3 (of 3 total)