I'm going to start a project from scratch by using ezpublish 5. But i'm not sure do we need ezpublish_legacy (old version) if we dont use it? How to get rid of it for new project with only ezpublish5? I spent hours on google but not found the way to install ezpublish without ezpublish_legacy :(
Please help! Thanks!
The answer is quite temporary : no you don't need it for frontends siteaccesses if you feel confortable in building your website in the new ez5/sf2 way. However, you still need it for the admin interface because it has not been completely rebuilt yet, on top of the new eZ Publish 5 stack. So unless you don't need an admin interface or are planning to write your own, then you need ezpublish_legacy :)
eZPublish 5 will always need ezpublish legacy.
We must waiting for eZPublish 6 to run without it. (from an eZSystem's answer)
Related
I want to upgrade laravel version from 3.1 to 5.x. What steps I need to follow to do this?
Approach I found based on research is
Moving 3 to 4 first and then from 4 to 5.
Fresh installation of laravel 5 and change my code accordingly.
There is no easy way to upgrade Laravel 3 to any other Laravels. There are quite a bit bottle-necks there
1. Laravel 3 is based on Symphony2 and mostly influenced from Sphinx, on the other hand laravel4-5 is based on Symphony3.
2. Core Laravel3 is build on base level, so everything you build in your application folder builds up on top of Laravel instance, but Laravel4 and 5 are a composer package. So basically you are using these packages along with others to build your system.
3. Laravel3 has bundles and Laravel 4-5 has packages. Bundles has been deprecated quite long time ago and most of them are not being maintained anymore. Building process and structure is totally different than packages work.
and this list goes on and on.
Like I mentioned at the beginning there is easy way for it. By easy I meant running a script and everything is brand new.
From views to application, to schemas and Eloquent, many coding style and structure is changed in Laravel4. So long story short, there is no upgrade documentation for 3 to others because the only way to upgrade is rebuilding the application with new way. Even if you find a script to automate most of your code conversions, you still need to go through bundles and find right packages, add them to your composer and find old usages of them in your code to replace with new way.
The laravel docs give pretty good guides on how to upgrade (you first have to upgrade to 4, then to 5).
But since Laravel 5 is so different in every way, I wouldn't be surprised it's actually faster just to rewrite everything. At the very least it's safer and more optimized!
It's my first question here on stackoverflow so please be easy on me.
I've been trying to set up the source for CKEditor so I can start contributing to this editor. I have followed this link: http://docs.ckeditor.com/#!/guide/dev_contributing_code but I got stuck on step 4 as I haven't got the following file: bender.js. I also need something called gruntfile for step 5. Do you know where I can get them from as when I fork https://github.com/ckeditor/ckeditor-dev, the following project does not come with them. Also, what IDE do I need to use to develop code? Sorry, for this question as it might seem a bit stupid but I come from the Java background and Node.js is really new to me, therefore I'm struggling a bit here.
Thanks for any help
There are no requirements regarding IDE, at the end it's all just text.
Regarding your problems: Make sure you're forking ckeditor-dev, and not ckeditor-releases repository. Only dev repository contains all the helpers like gruntfile.
The gruntfile is there so if you cloned CKEditor repository, you must have it.
Then all you need to do is follow up the instructions of CKEditor contribution guide closesly, and you're good to go!
Coming from eclipse, I am used to be able to move methods around in a file by simply dragging them around in the structure view (called overvew in eclipse).
I have noticed that it is not possible in RubyMine by default. Is there a way to enable it?
If not, is there a feature request for this?
All I have found yet is this: http://youtrack.jetbrains.com/issue/RUBY-2987, http://youtrack.jetbrains.com/issue/RUBY-9672 which considers only moving methods between classes,
Thank you
disclaimer: This started a copy of my attempt to get an answer on the JetBrains forum.
As #LazyOne said in his comment, there is an open feature request for drag&drop inside the structure view : http://youtrack.jetbrains.com/issue/IDEABKL-71.
It has been created in Feb 2005 and is not scheduled for any upcoming version, with only 11 votes so far, so no need to get your hopes up.
I'm using Magento 1.4.1.1 for my webstore. The payment processor supports only 1.4.0.0. I realized this only just now when I was dreaming up of opening the store. Duh! Poor planning.
What's the way out?
Will downgrading help? Wat are the implications of that?
Thanks for any and all inputs.
I am not aware of anyone ever having successfully downgraded Magento. That said, a few considerations:
Are you using version control like you should be? If so, you should have a copy of the site and database from just before the upgrade. You should be able to use this as a starting point. This is your most optimistic route by far.
If no version control, you can download both of the versions and use diff to get the changes. Doing this in reverse theoretically creates a backwards patch.
If you've stayed out of the core code entirely, the code change could be nearly as simple as replacing app/code/core.
Even if you do downgrade the code, the data structures between versions have probably changed, so you'll need someone experienced to find those changes and tell you have to back-patch your database. This is, to say the least, perilous.
Overall, I wouldn't want to undertake this task. As Anton said in the comments, you'll probably have an easier time getting integration done than reverting the changes.
Best of luck!
Thanks,
Joe
I want to ask one of those broad questions so please go easy on me. I know that phil is doing well with pyrocms but I would like to use pyro for my sites and also know how to write custom additions to the cms to suit my needs so what bums me out is how do you use it? where do i add my additions? how is it laid out? Like I said before go easy with me cos there is no documentation for pyrocms.
Thanks
I suppose this is one for me then :-)
modules can be added to the system by adding the folder to application/modules and copying the folder structure. To understand the modular structure better read the documentation for Matchbox by Zacharius K. I'm on my iPhone on a train so not going to look I up for you :-)
look a details.XML within the module to see how to set frontend/backend module type and when you have set a module with is_backend_sidebar clear the cache (or wait 6 hours :-p).
Documentation WILL come soon, my Internet has been down 2 months longer than expected so finishing v0.9.8 then documenting the lot will take a while.
Tweet or email me for more help.