As I stated prior, I am working to fix this, but know the issue is not exactly straight forward.
The problem comes when someone uses the same effect (with the same name) against multiple models (targets). When this happens, the system creates thumbnails for each model/effect pair. Gallery comes along and tries to figure out which thumbnail to show (when it has multiple to choose from). This creates something called a cartesian product in SQL and literally creates information from inferences (relations) that are not necessarily true. The true issue is that the thumbnails are not a product of just effects (and effects alone). The application of an effect to a model is what creates the thumbnail.
Back to gallery. Gallery is intended to be a listing of potential effects that can be applied to your models, showing you a thumbnail from someone else's model/effect pair. The problem is that you do not necessarily have the same model as the person who generated theirs and when you select an effect for copy and copy it (so we cannot automatically generate a target/effect pair for you), it ONLY copies the effects to your effect data, BUT does not apply a target to it (since you haven't been asked to associate the copied effect to a target yet). To realize the full effect of the copy, you will have to go to the effects page (selecting a target as you enter) and then selecting the copied effect and hitting submit (which in essence pairs the model and target together).
I am rewriting the code for gallery now. I will be removing the calls to a table that we generated and calling information DIRECTLY from effects table. One of the new database calls has a left join on text that is making it very very slow though. My current issue is determining which thumbnail to show you when I have an effect if there are multiple targets available (meaning the user has applied the effect to multiple targets). This choice is critical to both what image is shown and what information is copied.
Kurt
