Go to content

Go to employees

Go to search

Problems with TMCore EPiServerModule and PageTypeBuilder

Have you ever used the PageTypeBuilder in an EPiServer project? If not, you should definitely take a look at it.

Tore Gjerdrum
 

Some time ago I participated in project where we used the TMCore EPiServerModule and PageTypeBuilder. Whenever we mapped up new associations nothing was shown on the page. When we went back to the Topic Map tab everything looked fine. This meant that the associations was saved to the TMCore database, but not reflected on the page.

I had Networked Planet support do the same thing witout the PageTypeBuilder, and then everything worked as expected.

Here is a little description of the problem:

This is how the page looks like.

Associations before edit

I now wanted to add another "Prosjektdeltakelse". I went into edit mode and clicked the "Topic Map" tab. Here I added the the project "Er det farlig? giftig oppslagsverk for Klif" and clicked "Save and publish".

Associations edit

When I went to view mode nothing had changed. After lots of debugging and support help from Networked Planet, we finally saw this error message in FireBug.

Associations error

This error is probably caused by PageTypeBuilder doing something to the tabs before TMCore can publish the page and do a redirect to the "View" tab again. We did not have time to find out on how to get this to work. A workaround for this is to go to the "Edit" tab and click "Save and publish" after you have saved the associations on the "Topic Map" tab.

The result was as we expected.

Associations working

Tags:


Comments:

  1. Hi! I'm not sure how PTB could be/is the cause of this as it doesn't really do anything except replacing PageData objects after application start. That is PTB shouldn't "[do] something to the tabs before TMCore can publish the page and do a redirect to the 'View' tab again". With that said, everything is of course possible :) I would really appreciate it if you could look a bit further into this when you have the time? Perhaps you could try removing PTB temporarily from your project to confirm that it's what's causing this? If it is, I'll try to get my hands on a copy of the module and look into what's wrong :)
  2. Hi Joel, Thanks for the feedback. Networked Planet support just assumed that it was PTB making trouble because they got it working in a project that was not using PTB. I will install two sites, one with PTB and one without, in the near future and let you know how it goes.
  3. I just tested the same in two of my solutions, and had the same experience (one with and one without PTB). (Clicked Save & view after adding association). I don't think it is related to PTB, but to how the NWP module handles "unpublished" associations. If you check NWP-TMEditor or the database, you will see that the associations are scoped when you are deleting or adding associations until you publish the page. If you digg into the TopicMapQueryHelper.GetRelatedPagesByOneHop you will see that unpublished associations are removed from the resultset.
  4. Hi Svein Inge. If you click "Save and view", then this is the right behavior. If you click "Save and publish", then the page should be published and the TopicMapQueryHelper.GetRelatedPagesByOneHop should not filter away these associations. How does it work if you click "Save and publish" on both of your installations?
  5. If i Save and publish, the association scope are removed, and the associations are displayed. One of the sites (the one without PTB) have a custom(crappy) cache implemented, so I had to invalidate the cache to make the associations pop up. Both installations are running EPi5.
  6. Hi Svein Inge. Thanks for your feedback! Maybe we was to quick to blame PTB. I will try the same with my CMS 6 solution when I get the time.
Post a comment