I am a member of a team who try to build several sites using Liferay. We have difficulty sharing updates between us using LAR files and we have the same problem building the test and QA version of the site. We like to use something like traditional version control where each one download a version of the site, do some changes and update the repository. Is there a way to do something like this? We suspect that we are using the LARs in the wrong way or maybe it is not meant to be used like this. Any solution? Thanks in advance.
Back up your database, check that in to your version control, The restore the database.
All the information required for a Liferay site is in the database (and the custom plugins if you're using them).
So I'd use backing up and restoring the database as your solution.
Related
I have been working with Wordpress and Drupal for a while now, and something you have to do to maintain those CMSs is update themes, plugins, core, and modules.
My question is do you have to do that with the ExpressionEngine CMS? In the addons dropdown, there are modules, accessories, extentions, fieldtypes, and plugins. When I go to these, it doens't look like there is a way to update them. It shows what version there is, and I am able to delete them from there, but no updates anywhere in sight. Is it something I even need to do?
Thanks
Edit: I found the "update modules" button, but I still do not see anything like that for plugins, or anything else.
EE doesn't make it quite as easy as it is in WordPress. You could check out the Lamplighter extension to see what's still in need of an update then download from the respective source.
This is getting into opinion a bit but when I did a lot of EE dev, I usually stuck to the philosophy that if it worked, I used it and didn't worry about upgrading. Occasionally an extension/plugin would get a significant upgrade, a security patch, or have a feature implemented that I needed. That's That's when I'd go through the process of downloading and installing updates.
my Joomla-backend ist destroyed. i can do a log in in a normal way, but then i see only text, no graphics. and also the wohle site is not visible and i can't scoll it. i made a screenshot, please look at it to see what i mean. i have to upgrade my Joomla Version but i cant do it with this broken backend. The current Joomla Version is 1.5.26
So, how can i fix this? I need full acces to my backend. Please help.
This is why we should not use older version of joomla.
you must install newer version of joomla
It is more reliable and secure.
Here is the step by step migration process
I am new to sakai, i want to add my own tool in sakai source code like announcement,syllabus...etc That tool having some my own functionality for this what i have to do, how can i develop my own tool in sakai.
Thanks.
Use one of the archetypes to get you started, then customise it. When you are comfortable you can change the UI layer to be whatever you like.
https://confluence.sakaiproject.org/display/BOOT/Developer+Tools
If you are looking for a solid "base" tool shell to begin with tool development my recommendation would be to start here: "Sakai Wicket Maven Archetype". There are a few other very good archetypes available but are often outdated and may cause you some problems based on my experience. This has been the one I've had the most success with.
This uses Wicket but does not mean you have to use Wicket to develop further with it. Make sure to pull the 1.2 version as last check the binaries for the others were not available yet so replace -DarchetypeVersion=1.4.1 with -DarchetypeVersion=1.2 It will compile and deploy successfully as a tool "as-is" that you can modify as needed. It also allows you to code in Java to directly access the sakai API and pull from its database or even add your own tables. I've successfully used it with NetBeans 8.0.1 and MySQL 5.6 under Windows 7 with Maven 3.2.3 and Sakai 10.1.
The code is well-documented and is no-frills but with enough varied functional use examples to allow you to do "almost" anything you want. The wicket manual is 600+ pages but in my experience you should be able to accomplish a lot just by looking at the code in the archetype.
I wish to create a document repository for my company. Reason is because my company have many documents and they did not have a version tracking in place. This means everyone is using different version all the time.
Plone is something new to me and i got to know from a good friend of mine. And too bad he is not around anymore to answer my question. I believed in him and i wish to materialize his idea, to use Plone as a document repository for my company.
I have install Plone and manage to view the default Plone page, add all company's username and change the logo to my company's logo. And now the biggest question is, how to setup the document repository? What i have in mind was to create a "page" for the user to add files, download files, search for files and read its description.
Any lead for me to go about?
Reusable,
Same problem here. We started to use Plone as our main DMS 4 weeks ago (inserting existing docs at present).
For working copies, we use iterate (insert plone.app.iterate under eggs in your buildout.cfg).
For versioning, Products.CMFEditions. I believe this worked out of the box.
For creating new workflow, look into plone.app.workflowmanager and read the docs.
In a previous question we asked, we were still looking at Dexterity which has alot going for it but eventually we decided on adapting an existing content type based on Archetypes.
As for inserting files, as long as the description is ok, they will be found through the in-built search functionality, but you might consider using Iterate mentioned above to make sure that nobody is using the same file twice.
As your new, as I am, the docs seem hard at first but are actually quite good.
And this book is still giving me the foundation we need to keep adding functionality.
Good luck
I think, you should get pretty far with vanilla Plone installation, without developing your own extensions or other customization add-on-products. Therefore, I'd recommend you to start with Plone 4 User Manual to find out everything you could do out-of-the box.
As #Speediro mentioned, versioning support comes built-in for the main content types (and you don't actually see CMFEditions mentioned anywhere), but it's not activated for file uploads. Although, as briefly mentioned in the manual: Content items can be configured to have versioning enabled/disabled through the Site Setup → Plone Configuration panel under "Types".
Working Copy Support (plone.app.iterate) should also be there already waiting for activation on Site Setup's add-ons-panel.
Yet, before the Plone Collective (=community) Developer Docs or Professional Plone 4 Development, I'd recommend Practical Plone 3. It has a bit outdated graphics (because it was made for Plone 3), but it's great next step after the user manual. E.g. how to define content rules to send e-mails notifications for content updates (still through the browser without coding). Or how to create custom forms using Products.PloneFormGen.
When you really need to write your own code, it'd be time for Professional Plone 4 and the Collective Docs.
If you can't have a developer to manage your stuff, I would recommand to stay on official Plone, no custom code and use only widly used addons.
I mean:
stay on the default theme (sunburst)
use the default plone content types
only customize the logo
activate plone.app.iterate in the addon controlpanel
do not play with workflow because they need to know what you are doing. by default a file has the visibility of it's folder. It mean if you can see the folder you will be able to see all files inside. You can just activate default worklfow for files under the ZMI.
Use collective.quickupload addon
Your database will going really fast to a huge size because Plone is doing indexing and indexing means lot's of spaces. So you will have to handle this as system adminstrator;
Is there an extension that would check whether there are newer versions available to the installed extensions on a Joomla site, and would notify the site administrator?
Ideally, I am looking for something similar to Drupal's "Update" module.
I understand that there is no central place for keeping all these modules and their versions for Joomla, but at least a lot of them are available on the Joomla Extensions site, along with the needed information, so perhaps somebody wrote a tool that checks that source?
Aha, looks like this is to be included in Joomla 1.6, according to this description (check out the "Find Updates" button, looks great).
But if you are using Joomla 1.5 until 1.6 is stable check out: http://extensions.joomla.org/extensions/core-enhancements/installers/9332
Excellent for keeping components up to date :)