Posted 21 May 2014 - 04:16 PM
Hi Elise -
Thanks for the reply, update and effort. Yes - that is the plugin - glad you found it. It's not so much a case of not wanting to disable it. Ordinarily, I would have been very happy to if it were a simple plugin, but, as I explained, it was hard to configure. If I turn it off, I will have to repeat the process. I'm very sorry about not being able to disable it in my installation, but I thought that since you had also found another reproducible case with a different plugin, you were all set for local debugging/understanding the problem.
Please note that in my testing of this issue, it seemed like the membership add-on was getting lucky with respect to inherited css, since the expected fields that would control the display behavior were not present in its css. Also, as reported, it does not appear to work properly with Advanced Custom Fields. And, when I added some of the expected css info as shown in my previous posts, it was possible to correct the formatting, indicating that the membership plugin css info is missing, rather than being changed somehow or in conflict. If the fields were present, it would be working. At the QA level, when you find an outside product that changes the behavior of your product, it could be at fault, or it could be your product that is at fault - or maybe even both are at fault.
From a quality standpoint, the fact that another plugin reveals a possible shortcoming of or issue with the membership plugin's css implementation does not necessarily mean that it is the plugin at fault. In my opinion (and as a best practice), plugins should be coded/styled defensively for maximum compatibility.
I would appreciate it if someone in engineering would take a look at the membership css, review my comments, and see if it is possible to make the implementation more defensive, since the changes I made appear to work and point to a shortcoming in the design.
Alternately, if I am incorrect for some reason and the css fields I have pointed out as being missing in the Exchange membership plugin css are not actually missing, I would appreciate it if you could explain at a technical level why that is the case.
Thanks for your help.