I guess at some point we had Fw/1 2.2 and upgraded to 2.5. So developer set variables.framework.enableGlobalRC = true to work in 2.5 as 2.2.
So now my issue is we want to upgrade to FW/1 3.5 and not really sure how to remove this from out application. We did the wiring of DI/1 and that seems to work, but now we have the RC variables that are set in the setupRequest that are not available to the controller to reference.
Might be simple or complicated not sure at this point how to move forward. Any suggestions would help.
Thank you.
Related
I'm in the middle of developing a website using Sitecore 6.5 and when my company knew that Sitecore released version 6.6 they want to use the new version instead for the project, Is there a way to convert my Items created using sitecore 6.5(webform) to sitecore 6.6(mvc) so I wont redo my work?
General content items are not affected by switching to MVC .. it would be any presentation items that you would need to update if you did make a move to MVC. As #JayS says MVC is not mandatory and you can actually mix MVC and Webforms layouts within the solution so if you wanted to convert to MVC slowly over time it would be a possibility.
Just wanted to note that there is no such thing as 'recommended releases' any more (see: http://sdn.sitecore.net/support/versioning%20policy.aspx). Lots of customers already using 6.6 in production. The upgrade from 6.5 -> 6.6 should be straightforward (but this obviously depends on the complexity of your solution).
From my understanding, you do not need to use MVC in 6.6 if you do not want to. John West has a blog about the installer and how it enables MVC. You should be able to port your existing solution up to 6.6 relatively easily, but if you wish to take advantage of MVC you'll need to alter your solution.
Note, I believe that Sitecore has not marked 6.6 as a recommended release, so you may wish to inform your company of that.
UPDATE: Thanks to Stephen for pointing out that Sitecore has discontinued using the recommended release tagging. Some of their documentation online still needs to be updated regarding this :)
I have installed FaLang component to use multi-language support everything is working fine except the alias structure. When we are switching the language the URL not get changes as per the added alias conversion added into admin section. I tried almost all activities enabling both plugins but still the problem is as it is.
I believe Shaz is correct, there is no solution within FaLang at this time.
I asked the developer about this in Feb 2012 and he mentioned he was still working on it, but currently, with FaLang v 1.1.7 it still doesn't happen.
Initially I was really excited when FaLang appeared, but now I'm not so sure. I work on a lot of multilingual sites, and I don't want to get get stranded with multilingual Joomla 2.5 sites as has happened to me with many Joomla 1.5 sites I developed with JoomFish.
I know many well respected developers like FaLang, but FWIW I now favour the native language capabability built into Joomla 2.5. It's not perfect, but for now they have my confidence that it will improve.
Unfortunately this doesn't solve your problem, but if you need an introduction to how it works, here is one good link:
[http://bit.ly/LpPoV2][1]
and another one
http://www.youtube.com/watch?v=gnhVVtyejPg
Initially I found the process a bit cumbersome, but once I got used to it, it's works quite well ... and yes, the aliases work as you would expect.
Good luck!
I don't know what I was thinking and I don't have any kind of tests on this project. I want to upgrade it to 1.4 to be able to add to it all kind of different tests and have a more rigid project. What tips or recommendations can you guys give me?
Thanks.
I would recommend you to read through the release notes for each release to try to identify any areas that have changed that might break your existing code. Find them here https://docs.djangoproject.com/en/dev/releases/
Since you don't have any tests for your project you just have to roll up your sleeves and run full site tests where you run your app and try to test as many features you can to see if it is working as epxected.
I have just done the 1.1.1 to 1.4 upgrade (but I had some tests to help me) and it was not that bad.
There are 2 aspects of the upgrade. One is just to get your app to run on the new version and one is to change/update your code to utilize the new features in the 1.4 release. I would recommend that you first get it to work properly, release it and then refactor your code as you go along to use any new feature.
Is there any guidance on how to write modular Ember.js apps? I have seen Tom Dale's position on AMD here so I am not going to force fit AMD on to the framework (as some have attempted here). It appears that Ember internally uses bpm/spade. Is that a reasonable approach to modularize Ember apps too? Any samples using this approach?
P.S. The getbpm.org site seems to be down which makes it difficult to learn about it. There is a github page but it refers to the site for install instructions.
BPM in it's current form is no longer supported by the core team, but is community supported. The only build tools they are officially providing support for is rake-pipeline. However, BPM does still work and it works well (I still use it with my projects). For info on how to use it see this: https://github.com/ud3323/bpm/wiki/Using-BPM-with-Ember. You may want to use my fork of bpm too. I've merged in Joe West's support for a proxy middleware.
There is also community build tools for node.js called ember-runner which looks promising as well.
As for using rake-pipeline. Look at the AssetFile on the emberjs projects to see how must be configured using rake-pipeline and rake-pipeline-web-filters. Also, take a look at the answers to this question on StackOverflow (especially Yehuda's). You may also find this gist helpful as well.
Try Ember App Kit - maybe it would help you.
I have played a bit with Rails, so for me, creating a rails 3.2 app was the easiest way to achieve this. So if you don't mind using rails as a back-end, I this might suit you.
Perhaps ember-tools could help:
https://github.com/rpflorence/ember-tools
I am novice still I found yeoman and ember-generator useful. In future you might need to add tests , mock rest calls you can easily npm install sinonjs and npm install ic-ajax
From the homepage of django-mptt
Version 0.2.1 is not compatible with Django 1.0 and above - please use SVN trunk for now
I tend to avoid using trunk for work that is going live any time soon, But I have a rush job.
Does it work with Django 1.2, (beyond "hello world" equivalents) Does anyone have any current experience / odd bugs to share etc.
DJango-mptt on Google Code seems to have been abandoned, but there are a couple of forks on Github.
This one uses subclasses instead of registering the models, which makes in easier to use: http://github.com/bfirsh/django-mptt
However I'd recommend this fork, actively developed by one of the FeinCMS developers, which I've used with Django 1.2:
http://github.com/matthiask/django-mptt/
I'm using the trunk version since Django 1.2 is out and haven't run into any problems with that! Can't promise you that it will work for you; for known issues have a look at their tracker: http://code.google.com/p/django-mptt/issues/list