Error while adding ContextHub to the page component - aem

We are working on the AEM 6.3.
We have used Context Hub Parameters on Adobe Target Framework within Adobe Target cloud configuration.
However, when we have add the following line to add ContextHub to our page component:
sly data-sly-resource="${'contexthub' # resourceType='granite/contexthub/components/contexthub'}"/>
I am getting error on the console as shown below:
I tried resolving this but the effort was in vain.
Can anyone help me regarding this ?
Do we need to add some dependency for ContextHub in our clientlibs?
Thanks !

add the following clientlibs to your website and the error would go away.
granite.utils and granite.jquery
Hope this helps!!

Add this line also where you are including contexthub
data-sly-call="${clientlib.js # categories='granite.utils'}

Related

Error while using node module in SAP UI5 app

The requirement is to use of the node modules in my controller file of a UI5 app. I've installed the module and it resides in my npm_module folder. Based on the below blog, I've added some configurations in my ui5.yaml, yet I get the error pasted below.
Can anyone help me in this regard?
Blog Referred: https://blogs.sap.com/2020/07/30/project-shims-using-npm-modules-with-ui5/
Code screenshot
Error: failed to load 'thirdparty/aws-sdk.js' from resources/thirdparty/aws-sdk.js: script load error
Update: The issue was the path mentioned in the controller. I changed it to refer to the dist folder where the actual aws-sdk.js existed. And it resolved the error.

TYPO3 backend form module gives error when creating forms

I'm currently running TYPO3 version 8.7.18 and running a site_package that was made by using the site package builder: link
Whenever I try to add a form by using the default backend forms module I get the default message Oops, an error occurred! along with that the following error
TYPO3\CMS\Form\Domain\Configuration\FormDefinition\Converters\AddHmacDataConverter not found
Searching for the issue I get several hits on the Gitlab but these do not provide any solution.
Along with this setup, I've added the forms module as a static include in my top-level template.
do you have a composer installation or an extension manager build up?
If a class is not found you may need to rebuild the autoloader information.
My error turned out to be caused by a corrupt installation. I've had to upload the file AddHmacDataConverter.php in the following path /public_html/typo3/sysext/form/Classes/Domain/Configuration/FormDefinition/Converters. A very weird error indeed.
For those that came here with the same error, make sure to check that folder. Apart from that add the news as a static inclusion in your top domain. You could also follow #Bernd Wilke's idea which s to disable the extension, clear all system caches (and additionally remove typo3/temp/autoload and then active the extension again.

Config.yml Using Plugin LobbyCompass giving error

I am having this problem: I have configured my config.yml on a plugin called LobbyCompass, its a plugin on minecraft for my server and its version v2.5
This is the error I am getting when I try to open up the compass:
[.17:27:58 INFO]: [LobbyCompass] A open-compass error has been thrown. Please check your config or contact a developer if the problem persist.
I do not think this is a problem with the plugin and I think this is a problem with my config.yml. Could somebody fix this for me?
https://hastebin.com/iqegomegam.coffeescript
I think I know how to help you, there are multiple situations, if none of them described here help then please comment on what your situation is
1) If you have a plugin you will have to go to the plugin.yml and in that file you will have to add this line
dependent: LobbyCompass
2) If you have a server then in the server.properties you will have to add this line of code
depend: [LobbyCompass]
3) If none of those work then go in the game with that error and type in /plugins. If LobbyCompass is there then you must contact the developers because there is an error, or you can download a different version of the plugin. If it is not there then you must delete the plugin, delete all cache and then reinstall the plugin.
For all of those solution you must remove all other plugins and their configs temporarily

The absolute uri cannot be resolved : Custom Tag Issue

I am facing one problem when my code goes to publish. I have page in which i used a component with custom tag. It work fine in author, but when i replicate my code from author to publish it gives error like : The absolute uri: http:||www.mysite.com/taglibs cannot be resolved in either web.xml or the jar files deployed with this application . I have correctly replicated the my /apps/mysite folder on publish. But it gives error on publish but not on author.Any troubleshooting steps that can help me?
Thanks
Make sure that bundle with your custom tag library was installed correctly on publish enviroment (via /system/console/bundles).
And, could you describe how you deploy your project on publish enviroment?

CKeditor plugin not working

I tried to setup the media Plugin from
http://forge.clermont-universite.fr/wiki/ckmedia and http://forge.clermont-universite.fr/projects/ckmedia/files
When including
CKEDITOR.config.extraPlugins = 'media';
in my page I get an error
Error: uncaught exception: [CKEDITOR.resourceManager.load] Resource name "media" was not found at "http://localhost:8080/fileupload/ckeditor/plugins/media/plugin.js?t=B49E5BQ".
Please check, the directory name. It should be 'Media' or 'media' according to your media plugin file. On unix/linux systems... it matters. I was also facing problem on godaddy hosting but after looking at MediaEmbed plugin file, i find out that it was MediaEmbed not mediaembed.
There was a file not found error for that file.
Right click on the Tomcat server in Eclipse and choosing "Clean..." solved the problem.
We were getting this error because our node add/edit forms were being rendered within the website's theme, which may include a lot of unnecessary and/or incompatible javascript. For reliability, we switched to using the administration theme (in our case bartik), and then the javascript error disappeared. Hope this can help someone else out there.
you should keep your plugin files(plugin.js, css, images) under <plugin-name> along with all plugins of ckeditor. See how core plugins are organised.