Tracking Plugin failing with error No bean named 'i18nResolver' is defined

  • 2
  • Problem
  • Updated 1 year ago
When trying to use the tracking macros such as tracking info, the following error is shown.

Error rendering macro 'tracking-info' : Failed to find component: No bean named 'i18nResolver' is defined

I looked in the add-on and there is a module named i18nResolver, however it does not allow me to modify of disable it. I recently upgraded to Tracking 4.1.0, because the license was not working for some reason for 4.0.0. We also recently upgraded to Confluence 5.9.10. 
Photo of Bill

Bill

  • 3 Posts
  • 0 Reply Likes

Posted 2 years ago

  • 2
Photo of Mervyn Toh

Mervyn Toh, Alum

  • 117 Posts
  • 7 Reply Likes
Hi Bill,

Can you provide me the storage format of an affected page? I'd like to replicate this on our test instance. You can get the storage format of the page via:

Menu (at the top right corner of the page) > Storage Format

Thank you.
Photo of Bill

Bill

  • 3 Posts
  • 0 Reply Likes
Sure copied below is the storage format. A tracking macro is used at the very end of the page.


<p><ac:structured-macro ac:macro-id="2452c5e7-55cf-44a2-b448-aba2ea539750" ac:name="toc" ac:schema-version="1" /></p>
<h1>New Wiki Spotlight - Creating JIRA tickets from the Wiki</h1>
<p>Looking to create JIRA tickets for your OKRs? With the upgraded wiki, you can create JIRA tickets when viewing a wiki page by selecting and hovering over text, and then clicking the JIRA icon. A JIRA issue is created with the summary text you selected and JIRA details you provide (project, issue type, description) and the JIRA issue is inserted directly into the wiki page.</p>
<p>&nbsp;</p>
<p><ac:structured-macro ac:macro-id="b182b477-202c-47df-a6be-5068ea768a44" ac:name="calendar" ac:schema-version="1"><ac:parameter ac:name="id">06f54cb2-0e00-4628-b697-371de3904f16</ac:parameter></ac:structured-macro></p>
<p><ac:structured-macro ac:macro-id="d48dc387-9042-47ad-a252-23a16a7b4652" ac:name="rw-search" ac:schema-version="1"><ac:parameter ac:name="spaceKey"><ri:space ri:space-key="@self" /></ac:parameter></ac:structured-macro></p>
<p>Fun to commence soon!<br /> <ac:structured-macro ac:macro-id="f18d2cdf-4aad-4649-baf9-3b76b86a94d1" ac:name="pagetreesearch" ac:schema-version="1"><ac:parameter ac:name="rootPage">KB:Web Portal Guides</ac:parameter></ac:structured-macro>&nbsp;</p>
<p><ac:structured-macro ac:macro-id="8771efd5-dfc8-43e3-bc79-84b0f5ea157c" ac:name="livesearch" ac:schema-version="1"><ac:parameter ac:name="spaceKey"><ri:space ri:space-key="KB" /></ac:parameter></ac:structured-macro></p>
<p><ac:structured-macro ac:macro-id="f390c8ce-00dc-4a5c-89eb-35ad7fb70ddf" ac:name="rw-search" ac:schema-version="1"><ac:parameter ac:name="spaceKey"><ri:space ri:space-key="KB" /></ac:parameter><ac:parameter ac:name="placeholderText">Search the BOOK</ac:parameter></ac:structured-macro></p>
<p><ac:link><ri:page ri:content-title="Test 2aaa" /></ac:link></p>
<p><a href="https://wiki.opower.com/display/~bill.franz/Test+2">Test 2</a></p>
<p><ac:structured-macro ac:macro-id="d29e7c44-6ba4-40ad-85d4-7e5e112613cf" ac:name="pagetreesearch" ac:schema-version="1"><ac:parameter ac:name="rootPage">KB:Web Portal Guides</ac:parameter></ac:structured-macro></p>
<p><a href="http://dro.deakin.edu.au/eserv/DU:30049080/strode-taxonomyofdependencies-2012.pdf">Test link</a></p>
<p><span style="color: rgb(0,0,0);">The table below lists the product slots available for this product.&nbsp;</span> <span>This reflects the latest information in Salesforce.</span></p>
<p><span> <ac:structured-macro ac:macro-id="a250101d-7cc0-402c-ad03-36b8ff8f6d75" ac:name="multimedia" ac:schema-version="1"><ac:parameter ac:name="name"><ri:attachment ri:filename="Architecture Video1.mp4" /></ac:parameter><ac:parameter ac:name="page"><ac:link><ri:page ri:content-title="Videos for New Engineers" /></ac:link></ac:parameter><ac:parameter ac:name="space">PD</ac:parameter></ac:structured-macro> </span></p>
<p><span style="line-height: 1.42857;">blah</span> <span> <br /> </span></p>
<p><ac:structured-macro ac:macro-id="0b5f8295-59fa-4fbd-8731-59282d87e273" ac:name="jira" ac:schema-version="1"><ac:parameter ac:name="renderMode">dynamic</ac:parameter><ac:parameter ac:name="server">OPOWER JIRA</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution</ac:parameter><ac:parameter ac:name="serverId">79be4952-72f5-3b08-9b7d-7076dcef0852</ac:parameter><ac:parameter ac:name="key">DOC-4048</ac:parameter></ac:structured-macro></p>
<p><ac:structured-macro ac:macro-id="dd4f8e91-009e-44d8-98c1-cf8c77790bf5" ac:name="jira" ac:schema-version="1"><ac:parameter ac:name="server">OPOWER JIRA</ac:parameter><ac:parameter ac:name="columns">key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution</ac:parameter><ac:parameter ac:name="serverId">79be4952-72f5-3b08-9b7d-7076dcef0852</ac:parameter><ac:parameter ac:name="key">DOC-3861</ac:parameter></ac:structured-macro></p>
<p><span>A product slot is a tool to help us ensure positive client and customer experience for pre-GA products while keeping our operational overhead for supporting them in check.&nbsp;</span> <span style="line-height: 1.42857;">For every pre-GA product, we evaluate the delivery dates and available Client Success resources for launching products.</span> <span style="line-height: 1.42857;">&nbsp;Each client to whom we decide to sell a pre-GA product to with a fixed delivery date gets a product slot.&nbsp;</span> <span style="line-height: 1.42857;">You can see the product slots available for all solution components at <a href="https://ticket.opower.com/secure/RapidBoard.jspa?rapidView=1634">Slot Request JIRA Board</a> </span> <span style="line-height: 1.42857;">. Slot requests are broken down by product on the <a href="https://ticket.opower.com/secure/Dashboard.jspa?selectPageId=15304">Slotting Dashboard</a>.</span></p>
<p>NextWeb BOOK Guide final checklist</p><ac:task-list>
<ac:task>
<ac:task-id>35</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Quick visual check of each page to make sure no images broke.</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>36</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Open every expand to confirm that content is displayed as it should be.</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>39</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Check every link on every page (anchor links, x-refs, See Also, etc)</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>42</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Check for extra carriage return on feature pages. This will need to be changed in the source.</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>40</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Remove &ldquo;DO NOT USE THIS PAGE . . .&quot; warning from top of each page.</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>43</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Add product section to landing page above it. For example, Alpha or Beta products would need to appear on&nbsp;<a href="https://wiki.opower.com/pages/viewpage.action?pageId=44643721">Exclusive Pilot Product Guides (Internal)</a>&nbsp;page.</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>44</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Add a link to that product on the&nbsp;<a href="https://wiki.opower.com/display/KB/Welcome+to+the+BOOK">Welcome to the BOOK</a>&nbsp;page</span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>45</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span>Add a link to the FAQ page for that product on the&nbsp;<a href="https://wiki.opower.com/display/KB/Product+FAQs">Product FAQs</a>&nbsp;page and&nbsp;<a href="https://wiki.opower.com/display/KB/FAQs">FAQs</a> </span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>51</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body>Add content to&nbsp;<a href="https://wiki.opower.com/display/KB/Product+Demos">Product Demos</a>&nbsp;(if applicable)</ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>52</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body>Add labels to each page</ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>53</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body>Add links to the guide on&nbsp;<a href="https://wiki.opower.com/display/KB/Solutions+Overview">Solutions Overview</a></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>55</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span style="color: rgb(34,34,34);">Add a section for that product to&nbsp;<a href="https://wiki.opower.com/display/PD/Opower+Products+101">Opower Products 101</a> </span></ac:task-body>
</ac:task>
<ac:task>
<ac:task-id>56</ac:task-id>
<ac:task-status>complete</ac:task-status>
<ac:task-body><span style="color: rgb(34,34,34);">If you've also added client docs, be sure you update the&nbsp;<a href="https://wiki.opower.com/pages/viewpage.action?pageId=17302978">Client Documentation (External)</a>&nbsp;page<br /> </span></ac:task-body>
</ac:task>
</ac:task-list>

<p><ac:structured-macro ac:macro-id="940f3365-b086-4478-ad79-9f2d7b7a713a" ac:name="tracking-info" ac:schema-version="1"><ac:parameter ac:name="value">view count</ac:parameter><ac:parameter ac:name="target">@self</ac:parameter></ac:structured-macro></p>
Photo of Mervyn Toh

Mervyn Toh, Alum

  • 117 Posts
  • 7 Reply Likes
Hi Bill,

On the target parameter for {tracking info}, can you remove the "@self" value. By default, if it's targeting the page itself, you don't have to set any value. Besides, "@self" doesn't seemed to be a valid value for the target parameter based on our documentation.

Thank you.
Photo of Bill

Bill

  • 3 Posts
  • 0 Reply Likes
I removed the @self and the error is still present. All of the related tracking macros seem to fail with this same error regardless of the parameters provided. 
Photo of Shane Arnold

Shane Arnold

  • 2 Posts
  • 0 Reply Likes
Just wanted to add a "me too". Confluence version is 5.10.4, and I have tried updating to most recently available tracking plugin version with no success. Further reading suggests it has something to do with classes not being defined within atlassian-plugin.xml, within the Tracking package.
Photo of Mervyn Toh

Mervyn Toh, Alum

  • 117 Posts
  • 7 Reply Likes
Hi all,

If you're still facing this issue, can you please send us a support ticket at support@servicerocket.com, and include the support zip for your instance. Here's how you can generate the support zip :
https://confluence.atlassian.com/doc/...

Thank you.
Photo of Zach

Zach

  • 1 Post
  • 0 Reply Likes
I'm having the same issue.  Was a resolution ever determined?
Photo of Shane Arnold

Shane Arnold

  • 2 Posts
  • 0 Reply Likes
Hi Zach,

In my particular instance, the issue was that a license was required to be installed. Please see below information supplied by ServiceRocket for my particular case;
Although Tracking is a free add-on, it still requires a license – the license is free as well. If you don’t have a license installed yet, you can generate a license for Tracking from our ServiceRocket Marketplace : 
http://marketplace.servicerocket.com/product/tracking-plugin
After downloading the license, go to the following path to install the license :
Confluence Administration > General Configuration > Tracking (left sidebar, under ServiceRocket Plugins section)

On the Tracking licensing page, upload the .key file. For the detailed steps on installing and licensing, you can check out our ServiceRocket Documentation :
https://docs.servicerocket.com/display/TRAC/Installation+and+Licensing