Error in Plugins: String could not be parsed as XML

Dear Joomlapolis-team,

today we made an update of the website www.sinnlichemassagen.org .

Now I have a problem to enter the plugin folder under "Community Builder" -> "Plugins". I get only "String could not be parsed as XML". There are no plugins listed.

I updated all Plugins, especially third party like geofactory or uddeim.

I think I have to analyse which plugin don´t work. What is the best way? Set the plugins in phpmyadmin "Published = 0"? Or do you have an other idea to fix this issue?

Thank you!
Mike

I have the same error message in backend on control center after the News of CB. I deactivated the module "Community Builder News". The news and the error "String could not be parsed as XML" disappear. But in "plugins" I have still the problem.

Joomla 3.6.4
CB 2.0.15
CB Subs 4.1.0

Sounds like you've a CB plugin installed with a broken XML file. Navigate to the below folder.

components/com_comprofiler/plugin/user/

Once there rename folders 1 by 1 by suffixing them with the word DISABLED to stop their plugins from loading. Keep doing this until the issue goes away and once it does the last folder you renamed is the plugin causing your issue. You can skip the following as they're core plugins.

plug_cbarticles
plug_cbforums
plug_cbblog
plug_cbconnections
plug_cbcore
plug_cbmenu
plug_pms_mypmspro

Thank you for your quick response!

I did it as you described, but I didn´t get it. I changed the folder and add "...-disabled", but it don´t work.

I checked all plugins from joomla an CB, no results. A few minutes ago I saw that the error disapears on C-Panel and in the plugin folder. I don´t know the exact action I did, but now it works. The error depended on your update feed "Community Builder Updates". I think you use the same feed for the plugin folder to show the version of the plugin. And now it is possible to open the admin modules "Community Builder News" and "Community Builder Updates", what was not possible a hour ago. Maybe you worked on this feed adresses?
Nevertheless, a long day comes to an end and the website ist working.

The error happens because an installed plugins XML file couldn't be loaded, which it loads to grab its plugin version to run the version checker. My guess is you disabled whichever plugin was causing the problem or maybe was a temporary issue due to server CPU hitting limits or something of the sort. Now that you can reach your backend I suggest ensuring everything is up to date.