I've recently upgraded my Orchard site to version 1.4. Since I had an source code enlistment I just updated to the latest Default branch, and built and deployed the new version. Since the deployment, my blog is totally missing. Thinking it had something to do with the new Autoroute feature, I enabled the Migrate14 module and migrated to 1.4, but still the blog is totally missing in both the Admin UI and at the site.
Do anyone have any ideas on what might have gone wrong?
Check if you have "Blog" feature enabled, this is the first thing.
Second - please check the logs in /App_Data/Logs for any exceptions being thrown and paste your findings here. This could give us a bit more detail.
Third - try upgrading your source to recent 1.x branch. I've been setting up a site using that one yesterday (also upgraded to 1.4) and everything went smoothly.
See this answer's comments for more information related to solution.
Related
we are using MPP14Reader to read tasks from Microsoft Project, and recently for some of the projects, we are seeing that getOutlineNumber is giving wrong value. (ex: in Microsoft Project OutlineNumber is 1.2 ,
where as task.getOutlineNumber() is resulting in 2.4).
going through MPXJ code, found that this has been fixed in latest release via commit https://github.com/joniles/mpxj/commit/628df2b4a9dc4f00f59c5d8ad1c54648292a5c41
looking at commit description, seems this is happening after Microsoft June Update !!
do we have any workaround here ? can some one please help
Not all projects have this issue, seems to be issue with some of the projects
This issue with MPXJ was recently fixed, as discussed here: https://github.com/joniles/mpxj/issues/107
I have upgraded Kentico site from Kentico 8.2 to Kentico 9.0, everything was looking pretty and working smoothly. But when I tried to export my own site, I got Exception with following statement.
“Conversion failed when converting from a character string to unique identifier”.
From your current description it is impossible to tell what might have broken. The exception you are getting is very common and you can find many examples of reason why it happens here in SO.
However, what might be related to your question in Kentico is whether the upgrade you performed was successful. Try checking CMS_SettingsKey table for following KeyNames
CMSDBVersion
CMSDataVersion
Are they both set to 9.0? If not, the upgrade was not entirely successful. If yes, then there is some other issue within the data in your database for which we would need much more information.
Some of the class form definitions haven't been upgraded properly. Try the upgrade again and make sure you perform all the Steps after upgrade, especially "Running the website - First request".
I'm trying to install Nwazet Commerce with Orchard 1.7.2.
Suddenly, nothing happens. No new menus, no errors, nothing in the logs, nothing. It is just as if I hadn't installed it.
Before you ask... yes I've enabled the modules.
I can't find even a single scrap of documentation. What is supposed to happen? I would expect to see some extra menus or something on my dashboard or perhaps some extra content types, but there's nothing.
Help please :-|
You can't. The current version in the source repository is only compatible with the 1.x branch. See https://bitbucket.org/bleroy/nwazet.commerce/issue/20/update-to-17
I have a version for 1.7.2 unfortunately I don't know what fork it was from so I don't know what bugs or issues were included.
I found it in my saved orchard files and tested quickly you will get the admin options.
Download available here
I want to know how to apply the issue changes done in the Liferay Issues can be applied in our portal.
For example my issues are cleared in the following links,
https://issues.liferay.com/browse/LPS-14417?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
https://issues.liferay.com/browse/LPS-14220?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
I want to apply the issue changed in the above links in my portal.
Please some one help me to achieve this.
Thanks in Advance.
Regards,
Dinesh M K
You have to see the resolution and fix version stated.
the second issue says :
Fix Version/s: --Sprint 12/11, 6.1.0 CE RC1
and that means that the issue was solved in all Portals after version 6.1.0 CE.
the first issue , is no longer reproducible, and duplicate of https://issues.liferay.com/browse/LPS-14220 which is again solved in 6.1.0 CE RC1
In other words, If your portal is older than this version, you can't do anything. You'll have to upgrade to version 6.1.0 RC1 or later
It seems that the fixed-in version is a bit weirdly set in those issues - e.g. LPS-14220 is a subtask of a story in LPS-14414, which is stated as completed for 6.2.0. Careful: I did not fully read through all of the issue's descriptions, links and mix what I read with the answer (and comment to) #yannicuLar gave
Basically, this seems to be a new feature. The way to backport it to your installation is to identify the relevant commits (e.g. download the repository from https://github.com/liferay/liferay-portal or https://github.com/liferay/liferay-plugins, identify the relevant commits (they all contain the LPS number), "backport" them (e.g. see if they can just be applied to your codebase or if they need manual adaptation because the whole code changed.
Some features are easier to backport than others, I can't tell about the complexity for this one.
In order to separate your changes from Liferay's core changes, you should try to implement this in plugins (or patched plugins) rather than changing the original code and recompile. Most likely it's only the kaleo-web plugin that's effected, but if there are core changes, you'd be better of having them isolated in plugins.
The simplest (and most futureproof) possibility is to wait a bit for 6.2 (RCs are already out) and upgrade your portal to this version. If you want to stay on a version that gets updates, you should do this soon anyway.
We have a liferay portal running on a hosting company, and We want to bring it to our own structure. So, I've downloaded the excellent bitnami stack and loaded it in our vmware server.
I've no experience on liferay whatsoever, all I know its that it uses mysql as database. Is there any docs on how to do it?
Tks!
Use the Liferay's Wiki:
5.0 to 5.1: http://www.liferay.com/community/wiki/-/wiki/Main/Upgrade+Instructions+from+5.0+to+5.1
5.1. to 5.2: http://www.liferay.com/community/wiki/-/wiki/Main/Upgrade+Instructions+from+5.1+to+5.2
I recommend to do a 2-step upgrade since direct upgrade from 5.0 to 5.2 is more troublesome.
There have been reports that it's some work to upgrade older versions to the latest and greatest, so you should be prepared for some efforts.
That said, the way you should go is to backup the previous installation (e.g. all directories, database entries etc) and deploy that on your own server. This installation then is updated to the latest version by installing the latest version and pointing it to the data from the previous installation. During the first startup, liferay will (given sufficient privileges on mysql) update the database structure and everything it needs. Keep your backup ready and test thoroughly if everything is upgraded the way you intended it to be.
Also you need to keep an eye on your customized stuff - if you have portlets or other components that use the liferay api, you might need to upgrade those manually to take changed APIs into account.
Theoretically that should be it. I've heard of people having had some problems with this - but it all depends on your level of customization and utilization of features in liferay.
The liferay folks intend to circumvent this in future with their EE environment, where you get better defined upgrade paths and long term support with minor upgrades to your environment, keeping APIs and database requirements stable. I'd hope that even upgrades between major versions will benefit from this, but have not yet tried it.