pdf-system plugin only at frontend please
Posted: 22 Nov 2010, 14:37
Hello Jan,
I contacted you before about a conflict with the pdf-content plugin (which is actually a system plugin ) and the Admin-User-Access toolbar module (backend).
It seems the plugin is active at the backend again because the code to stop it working in the backend is commented out.
I'm going nuts with users who have this cinflict and just get a blank screen when they log into the admin. It's a lot of work getting these users sites (backend) functioning again after they enabled both module and plugin. (depending on what restrictions they set in AUA, sometimes only phpmyadmin and ftp can be used to be able to login again, which is obviously ticking of a lot of developers).
If only I could find out where the actual conflict is, so I could make a workaround. The problem is that I have never been able to reproduce this conflict on my development machine. I've only just seen it happening live for the first time.
Can you please, please, please uncomment that code again in the next release?
I contacted you before about a conflict with the pdf-content plugin (which is actually a system plugin ) and the Admin-User-Access toolbar module (backend).
It seems the plugin is active at the backend again because the code to stop it working in the backend is commented out.
Code: Select all
/*global $mainframe;
if ($mainframe->isAdmin()) {
return;
}*/
If only I could find out where the actual conflict is, so I could make a workaround. The problem is that I have never been able to reproduce this conflict on my development machine. I've only just seen it happening live for the first time.
Can you please, please, please uncomment that code again in the next release?