Hi PTN,

Just curious if you got that email I sent. I tested the system by sending a similar message to myself, and it took quite some time before it arrived. The heading was 'A message from the CoffeeCup forum administrators', and it ended up in the Spam folder. So you shouldn't be looking for something with my name in the heading.

Hello Inger, assuming you mean to my business email, on record here, then no I didn't receive anything to inbox/spam.

Inger sent one to my registered email and I got it straight awayto my inbox which considering I am in a remote part of Java and my internet speed hovers around 1 Mbps at the best of times.

The Search Assist in my browser gave the following information regarding Duplicate Class Errors. Perhaps it will help if there are different Symbols (rather than different instances of the same Symbol) including the same class in the SD project file.

"Understanding Duplicate Class Errors
Duplicate class errors arise when the same class is defined in multiple libraries or modules. This situation can lead to conflicts during the compilation process, causing your project to fail to build.

Common Causes
Multiple Libraries: The same class may be included in different libraries that your project depends on.
Version Conflicts: Different versions of the same library can contain the same class, leading to duplication.

Resolving Duplicate Class Errors
To fix duplicate class errors, follow these steps:
Check Dependencies: Review your project's dependencies to identify any libraries that may include the same class.
Exclude Conflicting Libraries: If you find duplicates, you can exclude one of the conflicting libraries in your build configuration.
Update Libraries: Ensure that you are using compatible versions of libraries to avoid conflicts."

Frank

A further thought: the error could be triggered accidentally when adding an element to a Symbol. Unless one sets up the class name of an element before adjusting any of its styling etc., the element temporarily gets a generic class name assigned to it (e.g. container-1). That temporary class name may have been used in another Symbol.

Frank

I cannot replicate that if I set up any element without giving it a specific class name then yes SD gives that element a generic class name, if I then add a other element (same type) and style that element without specifying a class name it gives it the generic class name +1 for that element even if it's the same styling. Even if it's been added to a symbol.
If I add another element of the same type and click in that elements "class" thingy if opens a drop-down listvof all the class name already assigned to that type of element
I have tried and tried for a long time now to get a message about duplicated class names. The only time I get something along those lines is if I add a component, that was created in a previous project, and the easy fix for that is simply delete the duplicated class name and rename that element from the drop-down list.
There is a fix for the empty components thingy but can't for the life of me remember it, (I'm not at home at the moment) but Inger once sent me something to fix this issue when it happened to me a few months ago.

Hi all, thanks for the input but looks like a corrupt RSD file, CC developers will try to replace the missing symbols from an old backup (2 x components stripped out as well). Having built literally hundreds of websites using SD, FF and RSD (been using many CC products for over 10years) this is the first time I've seen this happen but hey ho, I've been working in IT/design for over 25 years so this isn't the worst thing to happen. This was quite a heavy project file with 27 pages, and I had multiple backups, so worse case I'll reference the live website and reverse engineer one of those.

Hi Wayan.

You're completely right of course. SD prevents duplication of the temporary class names, and so it shouldn't happen by accident with those.

As you know, it doesn't prevent duplicate class names with different types of element. For example, a series of Paragraph elements, each containing a quotation from a different text, could have been given class names text-1, text-2 etc. by the project owner. The temporary class name of the first Text element would also be text-1.

Happily it seems that the correct explanation has been found, and sorting it out is in hand.

Frank