Admin CallBack Problem

Hi all,

I developed a module and overridden admin callback function to make links available in admin.index.

I installed the module in my old pc and I'm able to see the new voices listed.

I changed pc and I installed my module and I can't see the voices but f I call the direct url I can see the correct page.

CS version is the same: 10.5 SP1.

I take a look in the logs but I can't see errors and I don't know where to search for errors.

Does anyone have the same problem?

Thanks for support,

-Irene

Find more posts tagged with

Comments

Appu_Nair1

That to me sounds like a bad compilation. That is if you have done this logically and have had some experience doing oscript like in builder. The reason links would work is because they are separate objects

you are just making sure they can be accessed conveniently from admin.index. Livelink uses something called a registry so if the code was compiled and enabled it would show up in this like this.

Look in theattached screen caps and see if you can pinpoint it.

Best

Appu

From: eLink Entry: Content Server Development Forum [mailto:development@elinkkc.opentext.com]
Sent: Wednesday, September 23, 2015 10:26 AM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: [EXTERNAL]Admin CallBack Problem

Admin CallBack Problem

Posted byibernaus@altevie.com (Bernaus, Irene) On 09/23/2015 02:51 AM

Hi all,

I developed a module and overridden admin callback function to make links available in admin.index.

I installed the module in my old pc and I'm able to see the new voices listed.

I changed pc and I installed my module and I can't see the voices but f I call the direct url I can see the correct page.

CS version is the same: 10.5 SP1.

I take a look in the logs but I can't see errors and I don't know where to search for errors.

Does anyone have the same problem?

Thanks for support,

-Irene

[To post a comment, use the normal reply function]
Forum:	Content Server Development Forum
Content Server:	Knowledge Center

sıɹɥɔ

Hi Irene,

One thing to notice for this particular object is that they are registered by their name. (Appu nicely showed the code that does this! :-)

The effect of this is that modules need to have names for their admin page callback that are unique across the system. (The convention is to prefix the name of the object by the module name.) If you orphan the object but not give it a unique name then it will conflict with other modules: only one of the modules will appear on the admin page. So one possibility for what you're describing is that you've two modules, both with the same name for their admin page objects; you won't see the problem if only one of the modules is installed, but it will appear when both are.

Hope this helps,

-chris

Irene_Bernaus

Hi Chris, Hi Appu,

you were right, no doubt on it! :-)

I just renamed specified objects in my module and all worked fine, finally!

Thanks a lot for your help,

-Irene