Troubleshooting the DXCore/CodeRush plug-in loading
Sometimes CodeRush/DXCore plug-ins may not be loaded correctly. Here is a brief instruction if you’d like to investigate and fix the loading of the plug-in in question.
1) If you develop and compile the plug-in, make sure the plug-in is built into the correct folder. The output path should target to the Community Plug-ins folder. You can check the correct path by clicking the “Plug-ins…” button (or via the right-click context menu and choosing the corresponding menu item) in the “DevExpress -> About” dialog. On Windows 7 it may look like this:
C:\Users\Admin\Documents\DevExpress\IDE Tools\Community\PlugIns
If you got the plug-in from the DXCore Community or other (trusted!) place, simply copy the plug-in assembly in the folder above.
2) Make sure that the plug-in assembly is not blocked by Windows security. In the Windows Explorer, right-click the assembly and choose Properties window. On the General tab click the “Unblock” button if any:
DXCore requires this to properly execute the code in the plugin.
3) Inside the Visual Studio IDE, make sure the plug-in is loaded via the Plug-In Manager. Follow these steps to get to the Plug-in Manager options page:
1. From the DevExpress menu, select “Options…“;
2. In the tree view on the left, navigate to this folder: “Core”;
3. Select the “Plug-in Manager” options page;
4. Find your plug-in and verify its state – Loaded/Unloaded:
If the plug-in is not loaded,click the Load Plug-in Assembly button:
If the plug-in is loaded, make sure that all required items were registered on the right side of the Plug-in Manager options page, for example:
4) If the plug-in was not loaded or does not provide the desired feature, make sure that the feature is enabled. The plug-in may provide an options page which enables or disables the feature. If there is no options page, we can find other plug-in loading clues in the DXCore Message Log window.
By default, the message logging is disabled. You can enable it on the Messages options page in the Diagnostics category of the Options Dialog. After message logging is enabled, restart the Visual Studio IDE, open the Messages tool window from the DevExpress | Tool Windows | Diagnostics | Messages menu item and find out what’s going on with this specific plug-in.
If nothing helps, the DevExpress Support Team is the best source to contact for a help.
—– Products: all Versions: 11.2 and up VS IDEs: 2008 and up Updated: May/15/2012 ID: T055
Fatal error: Uncaught Error: Call to undefined function eregi_replace() in H:\root\home\megazoid-001\www\skorkincom\wp-content\plugins\bbcomments\BBComments.php:41 Stack trace: #0 H:\root\home\megazoid-001\www\skorkincom\wp-includes\class-wp-hook.php(289): render_comment() #1 H:\root\home\megazoid-001\www\skorkincom\wp-includes\plugin.php(212): WP_Hook->apply_filters() #2 H:\root\home\megazoid-001\www\skorkincom\wp-includes\comment-template.php(1028): apply_filters() #3 H:\root\home\megazoid-001\www\skorkincom\wp-content\themes\inove\functions.php(1163): comment_text() #4 H:\root\home\megazoid-001\www\skorkincom\wp-includes\class-walker-comment.php(179): custom_comments() #5 H:\root\home\megazoid-001\www\skorkincom\wp-includes\class-wp-walker.php(144): Walker_Comment->start_el() #6 H:\root\home\megazoid-001\www\skorkincom\wp-includes\class-walker-comment.php(139): Walker->display_element() #7 H:\root\home\megazoid-001\www\skorkincom\wp-includes\class-wp-walker.php(332): Walker_Comment->display_element() #8 H:\root\home\me in H:\root\home\megazoid-001\www\skorkincom\wp-content\plugins\bbcomments\BBComments.php on line 41