My agency is developing using the CE version in anticipation of purchasing a license. We are creating xforms by hand using the 2019 CE version, using jsp's in a Java tomcat application (separate deployment). I downloaded the 2020 version (hoping to use the 5.x version of TinyMCE) and found that rich text controls no longer appear using the same xforms used with the 2019 version. Looking at the browser page inspector (Ms edge), it appears that the TinyMCE resources (js and css) aren't downloaded to the browser at all. No html elements are created for the editor. I didn't see a console error or see an http error for the resources.
I couldn't find any issues related to TinyMCE in this version. Has anyone else seen this? Is there a configuration difference between the versions that may be causing it? (I reused the configuration I had from 2019 version). Anyone have suggestions on what to look at?
When I reverted to the 2019 version it works again. Any help would be appreciated!
I am not aware of any issue with the TinyMCE and Orbeon Forms CE 2020.1.2. I would recommend you try to reproduce this with an out-of-the-box install, and if it works there, progressively put back your existing configuration on that out-of-the-box install.
If you are doing this with the perspective of using Orbeon Forms PE, I would just use the latest release of Orbeon Forms PE 2020.1.3 with a trial license, as this way you'll have a configuration that is as close as possible to what you're ultimately planning to have, and you will benefit from having all the latest released fixes.
(And should this not solve the problem, feel free to post more information in the comments.)
Related
I have downloaded and installed the Entity Designer Starter Kit on both VS 2010 and 2012. I've created a project and have customized that project to allow me to add (for now) three attributes for each field value: See Below: (I'd post the image but I've only started posting here and I don't have 10 points) :(
As you can't see above, the Extension is working...on VS 2010, however, we need to use VS 2012 - so we can have the new support for geography fields in our Model, but it doesn't seem to work in VS 2012. The extension shows up as an installed extension in the Extension Manager in both versions, but doesn't work (or do anything in 2012.) when we build a new Model or open an existing one. :(
I've looked at the manifest for versioning info, and it DOES show up in the Extension Manager as having been installed (in both versions). (See part of Manifest below -- We are using the Professional version of 2012)
<SupportedProducts>
<VisualStudio Version="11.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
<Edition>Express_All</Edition>
</VisualStudio>
<VisualStudio Version="10.0">
<Edition>VSTS</Edition>
<Edition>VSTD</Edition>
<Edition>Pro</Edition>
<Edition>Express_All</Edition>
</VisualStudio>
</SupportedProducts>
Does anyone have any idea why its not running in 2012?
Thanks for any help!!!!!!!
bob
Back in 2010 I found that the Starter Kit did not work, perhaps due to the version being for VS2010 RC.
So I rebuilt it, and today, I've just upgraded it to VS2012.
So you can get it from my Blog.
All I did was run it though the VS upgrade wizard, and then change the manifest to VS2012 and it worked fine. Perhaps you could explain a little more "geography fields", as I've not read up yet on any of the changes in VS2012.
http://www.jsrsoft.co.uk/blog/post/Entity-Framework-Starter-Kit-alternative
I installed WeBlog package from sitecore marketplace (http://marketplace.sitecore.net/en/Modules/WeBlog.aspx) in my sitecore instance. Initially i had trouble installing package however i retried again deleting weblog.config file. It installed without any issue however when i look into content editor i don't see any WeBlog Modules under Template, System or Layout sections.
Does anyone know why?
Thanks.
Which version of Sitecore are you on? Is the module compatible? Weblog shows that it's compatible with the following versions: CMS 6.2, CMS 6.3, CMS 6.3.1, CMS 6.4, CMS 6.4.1, CMS 6.5.
Assuming you're on a compatible version, I'd check to make sure the layouts and sublayouts that were in the weblog package were actually installed on your instance. Open up the zip file and check out what files should have been installed.
Failing that, have a look at the log files to see if there are any glaring errors.
As a last ditch, you may want to try publishing. It shouldn't really matter in your content editor view, but I view the "publish" feature of Sitecore like the "reboot" feature of Windows.
Does anybody have successfully working module in DNN 6 with the Ajax Control Toolkit?
My modules stopped working when we migrated from DNN 5.x to to 6.x.
Modules compile without errors but I am getting client side script error:
'AjaxControlToolkit requires ASP.NET Ajax 4.0 scripts. Ensure the correct version of the scripts are referenced. If you are using an ASP.NET ScriptManager, switch to the ToolkitScriptManager in AjaxControlToolkit.dll'
Seems like this is conflict with Telerik's controls, according to information that I have found. But I didn't find any info how to fix it.
You should be able to use older versions of the ASP.NET AJAX Control Toolkit, but once they start requiring the ToolkitScriptManager, you're out of luck with DNN (though you'll be out of luck with any version of DNN, since there's not a way to override the type of ScriptManager it uses.
Starting with DNN 6, they use Telerik's RadScriptManager. Previously, you could modify the core code to switch out for the ToolkitScriptManager, but now switching out might cause other issues.
It could work together, but you'll need do some modifications to the core of DNN.
Here the list of things to do:
Check that you're using latest version of .Net 4.0 binaries of AjaxControlToolkit (I was able to let it work for DNN 6.0.1 with Telerik 2011.01.519 and ACT September 2011 v4.1.50927)
Check that in your web.config you have assembly binding redirects for System.Web.Extensions and System.Web.Extensions.Design to the version 4.0
Take DNN source package, find Library\Framework\AJAX.cs, locate method AddScriptManager, instantiation of RadScriptManager in it, for the version 6.0.1 look into line 54. Add one more property initializer:
EnableScriptCombine = false. Compile it (in Release configuration, of course), take DotNetNuke.dll and drop into your DNN installation.
You should be done.
Credits goes to Telerik support, despite it's stated there that it should work out of the box starting from 2010.1.625. Not sure, did I get them wrong, or they just reintroduced this bug.
P.S. DNN support promises to release version 6.1.0 in November with updated Telerik controls, which should fix this issue, at least on their opinion.
Just checked with nuke 6.1 and the last version of jaxcontroltoolkit - still the same error.
It looks like it's not supported anymore. Sad:(
I used Business Desktop Deployment (BDD) to build my project. Scripts are written in python. The BDD I am having doesn't support Visual Studio 2008.
Please tell me what is the latest version of BDD which supports VS2008
where I can get more info about Business Desktop Deployment?
BDD is a mini-methodology related to acceptance testing and TDD (it does stuff higher up, but this is probably what you're doing).
From your question, it looks like you've been writing BDD scenarios or unit examples in Python. Visual Studio isn't a great tool for writing Python in. If you want to carry on in Python, try Vim, or you might be able to get a Python plugin for Eclipse or IntelliJ.
If you want to use Visual Studio to program, use C# or F#. There are a couple of great BDD frameworks - SpecFlow or TickSpec - which can help you.
More information, including a list of tools, is available on the Wikipedia page on BDD.
Otherwise, please clarify your problem. It doesn't make huge sense in its current form!
Edit: Well, I learn something new every day. BDD also stands for "Business Desktop Deployment", and is a Microsoft product. Here's a page with an update suggesting you should use Microsoft Development Toolkit. Hope that points you in the right direction. I imagine the tool we've been using, click-once, does something similar.
You should probably know that few people seem to recognise BDD as meaning anything other than Behaviour Driven Development in software these days. I've heard Binary Decision Diagram as well; not often though. Good luck in your search.
There's an article here that might help you with Business Desktop Deployment (BDD) versions. It's dated March 2009 and says:
Microsoft Deployment Toolkit 2008 Update 1 replaces all prior versions of MDT and BDD. It provides additional support for new OS versions and deployment scenarios and is the upgrade path for users of earlier versions.
The article points to the MDT 2010 download page.
Does no such plugin exist?
So to be clear, I realize that RedGate has their own SSMS SCC app, and I realize that VSS2k5 will integrate in. I'm looking to stay with Hg as that's where my source already is, and I'ld like to find something that my team can stay consistent with on their tools.
As is, I guess I'm going to have to just run it through TortoiseHg and a folder with manual maintenance. Which isn't terrible, but naturally it would be nicer if there was an app pre-existing that I could consume.
And no, I don't have the time or inclination to write one myself. Not before Summer 2011.
Thoughts or ideas?
There are two versions of HgScc plugin:
HgScc - uses old MS SCCI API, works with MS VS2005/2008/2010 and with some third party IDEs. Last version of this plugin was released in 2008. It is not actively developed anymore, because MS SCCI API is very limiting and does not allow a tight integration with Visual Studio.
HgSccPackage - uses MS SCC Package, works only with MS VS2008/2010. This version of plugin currently in active development.
To get the first version of HgScc follow the instructions here:
MSSCCI compliant Mercurial client
Red Gate SQL Source Control is looking into supporting Mercurial in a future version, http://redgate.uservoice.com/forums/39019-sql-source-control/suggestions/803713-mercurial-support-as-source-control-system.
SQL Server 2012 (Denali) is using the Visual Studio 2010 Shell as the basis for the new Management Studio. I haven't tried it yet but I am hoping that tools such as VisualHg will work in Sql Server 2012. I will update this post after I get on my laptop that has the 2012 SQL Management Studio installed.
Have you tried hgscc? I know it integrates with Visual Studio, but I haven't tried it with SSM