One Drupal module is already available and released in community(drupal.org) and developed by someone which is in Drupal 7 version.
Now I have upgraded this module to Drupal version 8.
So can you please help me with the steps to contribute this Drupal 8 module to community please?
Here is the page explaining how to contribute in development:
https://www.drupal.org/contribute/development
You can register and ask additional question there too. But since you upgraded other's person module I guess you should contact module author.
Is the version 5 of Plone finally having an official multilingual solution that work? I did try Plone 4 but no multilingual solution was official or was working properly. I hope Plone 5 fix the problem.
plone.app.multilingual is a standard part of Plone 5. After installing Plone 5, activate it via the "add ons" control panel of site setup. Then use the "Languages" control panel to set available languages and translation parameters.
For earlier versions of Plone, install Products.LinguaPlone via the usual add-on package mechanisms. While LinguaPlone does not ship with Plone 4.x, it is a well-supported content-translation mechanism and it does work (though plone.app.multilingual is much better). Translation of Plone's user interface does not require LinguaPlone; it is meant to support content translation.
Both solutions also support adding translation support for custom content types.
I'd like advice on the best approach to deploying Diazo to work with Plone 3. I know that plone.app.theming is out of the question for versions less than Plone 4.1 but we can't upgrade to Plone 4 yet as we need to port some code to Plone 4.x first but we'd like to benefit from the theming infrastructure of Diazo.
You can also run Diazo via any of the non-Plone deployment methods listed at http://docs.diazo.org/en/latest/deployment.html. You'll lose all of the Plone TTW integration, but if you can build and compile your themes by hand, you're all set.
plone.app.theming requires Plone 4.1. You may be able to use its predecessor, collective.xdv.
collective.xdv Installation documentation
I have been using flex builder plug-in. But now trial period has expired and looking for some other option which comes free. I am trying to install flash develop plugin for eclipse. In my attempt to install I am trying this page but donno what all plugins to install...http://www.flashdevelop.org/wikidocs/index.php?title=3rd_Party_Plugins ...Can some one please guide. The problem i am facing here is I am not sure about what is outdated and what is useful
FlashDevelop is a standalone application (windows only), as far I know there is no plugin for eclipse. If you are searching for an eclipse plugin, there's the commercial FDT, with a 30 day trial period.
A new FlashDevelop version (4.0) is about to be released and most plugins from the old version aren't compatible with the new one. So I unless there's a new list somewhere or some plugin explicitly states that it supports the new version, every plugin there is probably outdated. Anyway, many plugins from that list have been integrated in FlashDevelop. You can of course use the latests stable 3.x version if you need a particular plugin.
If you've never used FlashDevelop, you should just try the stable 3.3.4 or the latest 4.0 beta or the very latest developement build and see if you are missing some features.
You could always write your code in Notepad and use the command line compiler provided in the free SDK. It's not going to be as nice as any IDE, but it is functional.
Another option, if you are a student or unemployed, is to request a complimentary license to Flash Builder from Adobe.
Another option is to use Tofino, a Free Visual Studio Plugin for Flex Development. However, you'll need Visual Studio for that to work. [And I assume a Windows Machine].
FlashDevelop, as others have noted, is not an Eclipse Plugin as far as I knew. It is a stand alone tool.
Other IDEs for building Flex applications are:
Sapphire Steel Amethyst, which is a commercial Visual Studio
Plugin
FDT; which is an eclipse based plugin. I believe FDT5
will have a free / community option, but I do not know if it is
available yet.
IntelliJ, which many developers swear by.
And of course Flash Builder. I believe the previous three are all commercial plugins, so do not fill your "free" Criteria.
I'm planning to install Drupal. Is there any reason not to install the latest 6.x version as opposed to the 5.x branch? Are there any really good modules that are 5.x only?
Unless you have a 5.x module that you can't do without, and that you know is being worked on to upgrade to 6.x, just use 6.x. i.e. Only start with 5.x now if you know you have a upgrade path with your site to 6.x (and then 7.x). If the module isn't being actively worked on, it mean you'll be unsupported when 7.x rolls around, so you might as well solve the problem of doing without that module with 6.x now rather than wait till your site is developed and up and running.
I've found enough modules to happily run my site on Drupal 6.x I think the only 5.x module I miss is one that did very easy Google ad integration, and that may have been updated I just haven't checked recently. I don't get enough traffic to make the ads worth the time in setting them up, so I just use the search part of the ad campaign.
Drupal 7.x is under development now, so I would expect that anything that hasn't been moved from 5.x to 6.x is just not being developed anymore, and is probably not really that needed.
Ultimately, take a look at what modules you may need. With an account on Drupal's site, you can filter by install type. I found that 6.x is much easier to work with in some regards (managing and upgrading modules) and overall I've had a much easier time maintaining my site under Drupal 6.x than I did under 4.x or 5.x.
I also think that 6.x runs much faster.
My bosses were insistent on making Drupal 6 sites for clients as soon as it was released. This was a headache, because views and CCK were not done, as well as many other modules. Their rational was that we'd have to eventually upgrade to 6, and we wouldn't want to go back and redo these sites. It ended up that we had so many workarounds while using the development versions of modules that it was a pain every time we upgraded modules or core itself.
Thankfully, this is no longer the case. Views, CCK, and most other modules are now ready and stable for 6. The only module we use that hasn't been upgraded is eCommerce, and it doesn't look like it will be, since ubercart is pretty much the Drupal standard for commerce functionality.
We asked ourselves the same question several months ago (just before Drupal 6 was finalized & released)
Our office has limited development resources, and we had released a couple of D5 sites, and a D5 sales app.
We went with Drupal 6.
The decision came after considering the core of what we were interacting with. CCK & Views are the only die-hard critical components for anything besides a default Drupal install, and the level of participation and vitality of the projects was very encouraging.
The stuff that really, really matters, has been/is being ported over to D6, and the wow, this would be nice, p2 stuff is hit & miss.
If you're doing any module development, D6 is a winner.
If you're already very comfortable with D5, then stick with it.
I hope this helps.
The one significant CCK-related module that's not D6 production ready is filefield. This may not be an issue if you're not doing anything substantial with images and media, but might be worth considering if you're going to do any serious DAM. Otherwise, I think we're (finally!) to the point where it's making more sense to go with D6 than D5. Either way, it's definitely worth the time to architect the site according to your specific needs, figure out what modules you'll need and find out if any of them have yet to be updated.
The asset module is not available for D6 yet, not even in a development branch. I've heard a lot about its benefits as a single way to manage all kinds of media files, but most sites can probably happily do without it.
If you haven't been running Drupal before you could find that version 6 has the modules you need. Besides, modules gets ported and created every day so your missing modules could very well be on the way.
For me, the lack of a protx payment module was a deal breaker when choosing which version to use.
The best thing to do is get a full list of requirements before you start, and make sure it's all available in 6.
As a module developer, I feel that Drupal 6's API is more mature then version 5.
So even if you decide to choose 6, and then finds a module is missing, it will be easy to develop it to 6.
Now that I've used Views 2, I ain't ever going back (unless it's to revisit old projects).
I think now, all modules and themes that are of any worth have been migrated and now I'm seeing a trend of new (actually good themes) are drupal 6 only as are quite a few of the must have modules.