Annie Boccio

Hi Jashan,
I have two site using the plugin. This is from the generated widget code for the site with version 1.10.11 standard:

<div id="sidebar" class="sidebar widget-area">
	<div id="ai1ec_agenda_widget-2" class="widget widget_ai1ec_agenda_widget">
		<div class="widget-wrap">
			<h4 class="widget-title widgettitle">Upcoming Events</h4>
			<div class="timely ai1ec-agenda-widget-view">
			<div class="clearfix">
			<div>
			<div class="ai1ec-date">

This is the generated code from the site upgraded to version 2.0.4:

<div id="sidebar" class="sidebar widget-area">
	<h4 class="widget-title widgettitle">Upcoming Events</h4>
	<div class="timely ai1ec-agenda-widget-view ai1ec-clearfix">
	<div>
	<div class="ai1ec-date">

You can see that #ai1ec_agenda_widget-2 and .widget-wrap are not in the version 2 widget (before the h4 tag is called.) I use .widget-wrap in particular for styling the site.

Thanks for your feedback on this!

That did the trick, thanks! I guess I was both overlooking the obvious and hoping for some new “remove” function to materialize :).

Thanks for the response, esmi.

The Twenty Ten functions.php calls the Background function with only
add_custom_background(); with no arguments, nothing to leave empty. It simply turns on the built in functionality in WP3.0. This gets passed through my child theme. What I’d like to do is set up a road block in my child theme functions.php.
Is there an argument I could add that would tell my child theme to ignore this function?

In the meantime I’ve converted the theme to a standalone instead of a child theme to solve the issue but it’s not my first choice.

Thanks, that article was just what I needed, got it working!

Gangleri thank you- the site had been hacked.
The solution to my particular problem can be found in this thread.

SoundTrip – I think you are right, I had this hack and manually removing the line
(sorry removed code but it’s what SoundTrip mentions above)
from the wp_options table was what finally fixed it. So thank you.

I did have the wpinfo.txt file, and so far only one _old.jpg file, also two phantom WordPress users. It appears the hack took place on April 6. About to go through and check for code inserted into php, then hopefully that’s it?