Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Why does my ported plug-in conflict with itself?

New Here ,
Sep 09, 2010 Sep 09, 2010

I recently ported my CS4 plug-in to CS5 by creating a new XCode project with DollyXs and throwing my CS4 plug-in source files into the new project. After following the porting guide to resolve my compiler errors, I threw the ported plug-in into CS5, but I get the message

The MyPlugIn.InDesignPlugin plug-in conflicts with MyPlugin.InDesignPlugin. Try removing one of the two plug-ins from the Plug-Ins folder and restart InDesign.

Somehow my plugin is conflicting with itself. I used the same plug-in ID from my CS4 plug-in. I suspect there's some porting step I'm missing, or perhaps I need to modify my project in some special way. Please help!

TOPICS
SDK
1.2K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Sep 09, 2010 Sep 09, 2010

If you forgot to increment the prefix while declaring an ID for an object in the *.ID file of the plugin it will give you this alert because Indesign thinks(at load time) that two different plugins are using the same plugin prefix when in fact there is only plugin present.

Wrong:

DECLARE_PMID(kClassIDSpace, kMyBoss,      kmyPrefix + 5)

DECLARE_PMID(kClassIDSpace, kMyBoss2,    kmyPrefix + 5)

Correct:

DECLARE_PMID(kClassIDSpace, kMyBoss,      kmyPrefix + 5)

DECLARE_PMID(kClassIDSpace, kMyBoss2,    kmyPrefix + 6)

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 09, 2010 Sep 09, 2010

I've triple-checked my object IDs, and all of them are unique within their ID space. This doesn't appear to be the problem.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Mentor ,
Sep 09, 2010 Sep 09, 2010

Do you have an older copy of the plugin around?

Also see other paths as specified via plugin config.

Then re-check the IDs, but this time for mismatches in the IDspace constant!

Dirk

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Sep 21, 2010 Sep 21, 2010

Using the debug version of InDesign, I was able to find that I had an incorrectly defined startup/shutdown class in my resource file. I'm not sure if the resource compiler should have flagged this somehow. Anyway, the plugin conflict was a strange way for this problem to manifest.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Contributor ,
May 15, 2014 May 15, 2014
LATEST

Just adding what I witnessed. Re-declaring a class in your plug-in's .fr also throws this error. Wasted 4 long hours. Hope someone else benefits.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines