bobbingwide

A fix for this problem has been applied in oik version 1.16
I also made a (silent) movie creating the problem and showing the recovery using the website’s control panel (cpanel)
https://www.oik-plugins.com/tutorials/recover-from-a-wordpress-fatal-error-using-your-sites-control-panel-cpanel/

I raised this topic a long time ago as a prompt to myself to cover the questions of styling the output from the oik shortcodes. The simple answer is NO – don’t change oik.css. Use a custom CSS file – which you can create and maintain using oik functionality. Note: You should create a different custom CSS file per theme.

It’s not necessary to use a child theme though I do recommend it especially if you generate themes using Artisteer.

With regards the the [bw_address] shortcode there is now type parameter for the shortcode where you can define your own text.

Hint: during site development you may want to use the [bw_editcss] shortcode to provide easy access to the custom CSS.

You can see examples of bw_address and bw_editcss here https://www.bobbingwidewebdesign.co.uk/oik_presentation/why-use-shortcodes/better-by-far/

Hi David, that’s a feature of oik.
see https://www.oik-plugins.com/oik-shortcodes/bw_pdf-list-attached-pdfs-shortcode/

You can turn it of by creating some custom CSS that overrides its behaviour.

Visit oik options > options to set a custom CSS file
Type the custom CSS file name ( e.g. custom.css ) and Save changes
Visit oik options > overview and click on the Edit Custom CSS link
Insert this CSS
a[href*=’.pdf’] { background-image: none; padding-left: 3px; }

Alternatively take a look at the link to see how I do the same sort of thing using the [bw_pdf] shortcode.

Herb
PS. In a future version of oik, the inclusion of oik’s styling (oik.css and bwlink.css) will become optional.

I have documented the problem and a workaround that you can apply here: https://www.oik-plugins.com/2012/08/fatal-error-call-to-undefined-function-oik_require-in-oikadminoik-header-inc-on-line-2/#more-2168

I applaud your pragmatic fix. If you have not activated the oik plugin then the problem would appear to be resolved… however you would not get any of the oik-header functionality.

And if you did activate oik then this would lead to a further fatal error when you attempt to add a new post or page
Fatal error: Call to undefined function textfield() in oik\admin\oik-header.inc on line 61

I have now documented this problem, how to recover from it and a workaround for the future here: https://www.oik-plugins.com/2012/08/fatal-error-call-to-undefined-function-oik_require-in-oikadminoik-header-inc-on-line-2/

This problem was fix in oik-nivo-slider version 1.5. For an explanation of the problem and how to recover from it see. https://www.oik-plugins.com/2012/07/oik-nivo-slider-v1-5-now-on-wordpress-org/

This problem was fixed in version 1.5 of the oik-nivo-slider plugin.
See https://www.oik-plugins.com/2012/07/oik-nivo-slider-v1-5-now-on-wordpress-org/

Hi, I only tried using blogger importer a couple of days ago and suffered the same problems as doniree.

I was innocently attempting to debug these on a local install when I noticed v0.5.

So I cleaned out the site (using phpMyAdmin) and tried again. It very nearly worked: 2831 of 2832 posts imported AND 693 of 697 comments.

I’m going to backup and drop the whole site and try again though. I don’t really want to trawl the posts to find out which one’s missing.

Hi, I had a problem on Multisite where oik-nivo-slider was not able to detect oik. I thought I’d fixed that in oik version 1.13 but it seems there’s still a problem with detecting the version.

The simplest fix, if you can do it, is to edit the oik-nivo-slider.php file and comment out the penultimate line of code so that it looks like this:
//oik_nivo_lazy_activation( __FILE__, $depends, "oik_nivo_inactive" );
When you visit the Site’s admin page you should see the Nivo settings page under oik options.

You should find that you can use the [nivo] slider even though it’s producing the warning messages on the network admin’s plugin list.

The message was caused by the underconstruction plugin which is passing a value of 8 as the third parameter ( $capabilities ) of add_options_page(). Changing this to “manage_options” eliminated the Notice:

Hi, I’m sorry about that. I don’t (didn’t) actually use the Plugin Dependencies plugin; I just thought it was a good idea so I coded the Depends: lines… wrongly.

The workaround to your problem is to either comment out the Depends: line in oik-nivo-slider.php or change ‘oik’ to ‘oik base plugin’.

I’ll leave Plugin Dependencies active until I’ve sorted them out in my development machine.

In the next versions of oik and oik-nivo-slider I’ve developed a slightly different solution that allows the plugins to be activated but not necessarily work. oik-nivo-slider will report a warning message. The idea being that a future version of the oik base plugin will be able to offer to perform the upgrades for you.

BTW: In the next version oik quicktags won’t be a separate plugin.
You will be able to choose whether or not to have it active from the oik options > Buttons menu

Please let me know how you get on.

Hi, can you confirm the name of the function call?
bbboing is dependent upon the oik plugin.

Do you have the oik plugin installed, and is it activated?
What version of oik do you have?

The other plugin that comes with bbboing – called bobbing – is dependent upon oik AND bbboing.

Can you confirm that you are on WordPress version 3.2.1?

Could it be that your theme (originally) contained the following code

wp_title( '|', true, 'right' );

// Add the blog name.
bloginfo( 'name' );

// Add the blog description for the home/front page.
$site_description = get_bloginfo( 'description', 'display' );
if ( $site_description && ( is_home() || is_front_page() ) )
	echo " | $site_description";
... etcetera

If so, try commenting out the bloginfo line. The duplicate MyBlog should disappear.

wordpress-SEO suggests that the only code you need for <title> is a call to wp_title(”); So you should comment out the rest of the code.

IMHO: it would have been just as easy to add an
if ( isset( $GLOBALS[‘wp_the_query’] ) )
into wp_reset_query.
then no one would have to worry about _doing_it_wrong()

Note: This change was made in changeset 18995 on 18th October. The comment “new does not require by reference” applies to the first change made in query_posts(), but not to the second which is an assignment by reference. I’ve raised this as https://core.trac.www.ads-software.com/ticket/19412