We are using Tridion 5.3. A new machine has been setup for Content Manager server as well as content delivery server(.NET).
When we try to add SiteEdit script extension in MMC snap in we are getting error
"Object TCMSiteEdit.SiteEdit could not be created, please check the availablity".
Can anyone help us resolving this?
Can we assume you have actually installed SiteEdit? If so, which version? Typically running the installer will add the script extension to the MMC snap in automatically.
Related
In a project that I am working now, a new WIX setup project was added by a developer. When I'm trying to get the latest from the TFS that we are using for the code base, the newly added project is shown as incompatible and while building the solution following error is thrown:
Has anyone experienced this before?
In a typical team build, the TfGetSources activity will do a Get to retrieve the source files from TFS source code control. However the Get will set the Read Only attribute on all files retrieved, and any attempt to over-write any source code controlled file, during the build, will result in an Access Denied error.
Your new project is using the WIX toolset Heat.exe utility to generate the file C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs. This file is under source code control which means it will be read only. The Heat.exe utility is throwing the Access Denied error because it can't over-write this file.
One solution is to remove C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs from team foundation source code control. It is generated by heat.exe anyway, so doesn't need to be fetched by the TfGetSources activity.
If you need to keep C:\70_Suite\Accounting\IBS.Accounting.Setup\App.wxs under source code control, then a work-around would be to remove the read-only attribute from this file. This could be done in the Pre-Build Event Command Line in the new WIX project.
I know I don't have a m2e connector but I did configure the lifecycle mapping properly in the pom. In fact, it was working fine. But now, it keeps giving me the above error marker which indicates the goal was mapped properly but the invocation of the goal failed within eclipse. Manually executing the goal from the command line works fine (the resources generated properly). What could be the problem?
It seems to be an eclipse issue. This happened whenever I updated the plugin and installed it locally. I had to restart eclipse and clean the project to make the above error go away.
I have installed Magnolia WebDAV-2.0 and try to access the templates Folder /magnoliaAuthor/.webdav/templates/ with BitKinex. I get the error HTTP forbidden when I try to access the templates Folder ; See the following picture:
I read in JIRA, that WebDAV-2.0 Version fixes this Problem but I try it and get the same error. Calling http://localhost:8080/magnoliaAuthor/.webdav/templates with the browser Returns blank page, which mean for me that webdav is installed successfully. How to Access magnolia webdav?
See same discussion at http://forum.magnolia-cms.com/forum/thread.html?threadId=ea35f17c-2e59-4f54-bffd-f80515d42f61&page=1
The report from Magnolia devs was that testing with "Magnolia-5.2.4 with magnolia-module-webdav-2.0 on Windows and BitKinex version 3.2.3" all works as it should.
Also the original issue reported confirmed that all works fine as long as you have the latest version.
Pls try with the same version or double check you don't have any version conflicts.
When I am trying to build the plugin module using .\scons it is raising me errors. What might cause these types of errors...? Error is
postMessage() was not declared in this scope.
I am using pepper_16 version. Here is the procee I did
Installed Python and gave the path required(Installed in D drive as I do not have privileges).
Downloaded nacl_sdk.zip extracted in the same folder where I have installed python and updated the tools with nacl_sdk.bat update
Enabled NativeClient form about:flags window and executed the server using httpd.py file.
And created project in Pepper_16/examples/TestApp using init_project.
Written the code as it is in the Getting started tutorial to test.
Then using ./scons in the same project folder in cmd mode I have tried to build
The above process worked fine for me where I have admin privileges. But the same procedure and same code not working where I do not have admin privileges.
Please let me know if any further details are required.
which source file was being compiled? a lengthier cut-n-paste of the output around the error message would help to give context.
also, when you say the plugin module, are you referring to NaCl itself or your own PPAPI plugin? normally NaCl's plugin is built into Chromium using gyp, and while scons can be used to build the NaCl plugin it is typically only used for testing, via the --register-pepper-plugin command line argument to chrome.
Using ASP.NET WebForms in Visual Studio 2010, and adding Glimpse to my WebSite (not WebApp):
I'm trying to install NuGet Package -> Glimpse.
The install is pretty straightforward:
PM> Install-Package Glimpse
Successfully installed 'Glimpse 0.79'.
Successfully added 'Glimpse 0.79' to
localhost.
But then I get an error in pink
Failed to generate binding redirects for 'localhost'. An item with the same key has already been added.
I got an error about a reference to "Microsoft.Web.Infrastructure", which I resolved by finding that DLL and placing it in the bin folder for my Website
Now I'm getting an http 404 error on http://localhost/websiteName/Glimpse/Config
I'm assuming the error is because the config file does not really exist there, and the route it tried to insert into IIS didn't work properly, so the page cannot be found.
Any help would be greatly appreciated, thank you in advance!
I'm a member of the glimpse team. Unfortunately, glimpse 0.79 does not support WebForms out of the box.
I expect that all the issues you have listed here will "disappear" once we have more official support.
If your really keen to get up and running, I recommend grabbing the source from gitHub.com/Glimpse and manually referencing Glimpse.Net.
I've also marked this SO question to make sure that we test out your use case when we are preparing to release with official support for WebForms.