Answers to the most common script issues.

Linkubaiter Script

Error when placing linkubaiter script in sidebars of wordpress template themes.

Warning: require_once() [function.require-once]: URL file-access is disabled in the server configuration……

With a second warning and a fatal error.

Answer: —–Use one or the other, both are not needed. ——

—-Option 1—-

allow_url_include

In the lsidebar.php file in the WP template replaced your code with the following:

<?php echo file_get_contents(‘http://my-domain.com.au/my-linkubaiter-dir/showlink.php?id=1‘); ?>

This method does not rely on “allow_url_include” to be set to “On” in the server configuration, so perhaps could be a preferred alternative to use in your documentation generally.

—-Option 2—-

1. upload and activate the Exec-PHP widget.
http://wordpress.org/extend/plugins/exec-php/
2. Add a text widget to your sidebar.
3. Stick the linkubaiter vertical/sidebar code into that text widget and save changes. Check out your blog where it should be working.

———————————————————————————————-

Error when using linkubaitor script on html. .htaccess solution not working.

I have tried the following solutions to get php to work on html files none of which work:

AddHandler applications/x-httpd-php htm html
AddHandler applications/x-httpd-php .htm .html
AddHandler applications/x-httpd-php5 htm html
AddHandler applications/x-httpd-php5 .htm .html
ANSWER:

Try the following:

AddType application/x-httpd-php .htm .html

—————————————————————————

Permalinks & htaccess in WordPress 2.6 & 2.7

ISSUE:

After setting permissions on .htaccess file to 666, WordPress admin panel -> permalinks says file is not writable after setting anything but default permalink settings. This is because WP is looking for the file in the wrong location.

ANSWER:

This is a common bug with WP 2.7 (and 2.6 from what I can see)
The issue is that WP has the .htaccess file in the wrong location.

Move the .htaccess file found at /domains/yourdomainname.com/public_html/cgi-bin
to /domains/yourdomainname.com/public_html/

Make sure this file’s permissions are 666.

Log back into the admin panel, set your permalink settings, click save settings and you shouldn’t get that error anymore.