I was notified yesterday by my provider that my site had been hacked and was distributing malware. I do hope that I was able to not only fix the malware issue but also identify and close the entry door.

If you notice anything strange please send me an email or comment here.

Kind regards,
Andreas

The small library provided is straightforward to use:

// include bridge functionality
require_once('./CodeIgniterBridge/Bridge.php');

$config = array('username'=> 'root',
'password'=> '',
'database'=> 'test.db3',
'dbdriver'=> 'sqlite');

// include CodeIgniter DB
require_once(BASEPATH.'database/DB.php');
$db = DB($config);

// custom factory class to instantiate DB_Forge
require_once(BRIDGE.'DBForgeFactory.php');
$dbforge = DBForgeFactory::Factory($db);

// CodeIgniter - create DB
$dbforge->create_database('test');
$dbforge->add_field(array('title' => array('type' => 'VARCHAR')));
$dbforge->create_table('test');

// CodeIgniter - create and show data
$db->insert('test', array('title' => 'A'));
$db->insert('test', array('title' => 'B'));
var_dump($db->select('title')->from('test')->where('title LIKE', 'A%')->get()->result_array());

$db->close();

Download: codeigniter_activerecord_172.zip

I’ve taken the time an revamped the plugin based on current Eclipse 3.5 and Mylyn 3.2 APIs.

To install the current version, you can use the Eclipse Timeline update site.

1. open about:config
2. create new boolean value extensions.checkUpdateSecurity=false
3. restart

The following code shows how to:


$proxy = 'http://user:pass@server';
$ua->proxy(['http'], $proxy);

# working, http & https
my $req = HTTP::Request->new(GET => 'http(s)://site/');
my $res = $ua->request($req);
if ($res->is_success){
print $res->as_string;
}


The tricky part is that lwp will still needs the http_proxy to handle http requests correctly, but not https_proxy as it needs to pass down the requests to SSLeay.

One particular feature of the Eclipse IDE is the framework for working with resource, more specifically the workspace resources. Michael Elder documented the Common Navigator Framework (CNF) in a series of articles in his blog.

Unfortunately, at the time of writing, CNF does not easily lend itself to use in RCP applications. A number of usenet postings and Eclipse bugs describes this problem. While a number of things still needs to be done to externalize the CNF API from the Eclipse IDE to allow clean use in RCP apps, a working solution exists today.

The following solution is derived from the sources mentioned above, full credit given:

1. ApplicationWorkbenchAdvisor
   
   public void initialize(IWorkbenchConfigurer configurer) {
   configurer.setSaveAndRestore(true);
   declareWorkbenchImages();
   }

   @Override
   public IAdaptable getDefaultPageInput() {
   return new NavigatorRoot();
   }

   public void preStartup() {
WorkbenchAdapterBuilder.registerAdapters();
}

   The code for declareWorkbenchImages() including declareWorkbenchImage() is copied from org.eclipse.ui.internal.ide.IDEWorkbenchAdvisor.

2. New NavigatorRoot class.

   The new NavigatorRoot implements IPersistableElement. This ensures that the class can be persisted when saving the workbench state. Otherwise, the navigator root element is not read when restoring the workbench state.
   
public class NavigatorRoot implements IAdaptable, IPersistableElement, IElementFactory {
public NavigatorRoot() {
}

   public Object getAdapter(Class adapter) {
   if (adapter == IPersistableElement.class)
   return this;
   if (adapter == IWorkbenchAdapter.class)
   return ResourcesPlugin.getWorkspace().getRoot().getAdapter(adapter);
   return null;
   }

   public String getFactoryId() {
   return this.getClass().getCanonicalName();
   }

   public void saveState(IMemento memento) {
   // TODO Auto-generated method stub
   return;
   }

   public IAdaptable createElement(IMemento memento) {
return ResourcesPlugin.getWorkspace().getRoot();
}
}

3. ElementsFactory Extension.

   To be sure the NavigatorRoot class can be instantiated when reading the workbench state, it’s createElement() method must be available. This is achieved in the previous chapter by implementing IElementFactory and now registering it in the elementsFactory extension in plugin.xml:
   extension point="org.eclipse.ui.elementFactories"
factory class="rcpCNF.NavigatorRoot" id="rcpCNF.NavigatorRoot"

   At this point the navigator is already fully functional- but does not yet show any data/projects or actions to act on the data.

4. Configure the Navigator

   To use the new navigator, the navigator must be configured and content needs to be added. This is done by using the org.eclipse.ui.navigator.viewer extension.
   Using this extension, we declare:

   1. Which viewer we’d like to configure (viewer).
   2. Which content we’d like the viewer to display (viewerContentBinding).
   3. And which actions to expose to the user (viewerActionBinding).

A working example with full source code is available here in this RCP Navigator Example (updated).

Download wp-cache_2.0.19_win.zip.

Due to user account control (UAC), CpuIdle is no longer able to access the registry keys required to allow CpuIdle to add itself to the programs run when Windows starts. No error message will be displayed, but CpuIdle also won’t start automatically. To work around this issue, the following options exist:

• manually add CpuIdle to the AutoStart group
• disable UAC in the Windows policies (this might cause security issues)

The third possible option would be to run CpuIdle with administrator rights (Right-click, Run As Administrator or use the compatibility options). The downside of this is that Windows does from now on display a security warning when starting CpuIdle.

Since Microsoft received a lot of criticism regarding UAC in Vista Beta2, we’re currently not rolling out an updated version with Vista support but will wait for Beta 3 and changes in UAC to be released.