Closed (fixed)
Project:
Open Atrium
Version:
7.x-2.x-dev
Component:
User interface
Priority:
Normal
Category:
Bug report
Assigned:
Unassigned
Reporter:
Created:
7 Jul 2013 at 06:23 UTC
Updated:
5 Feb 2014 at 17:50 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
hefox commentedI think the node titles are done via token intergration (entity token?) and it displays messages from message module?
Comment #2
m.schwarzenberg commentedWill you be so kind to export the view oa_recent_activity (to a textfile) if this works on your installation and annex it here?
I want to ensure that the view works correct....
Comment #3
hefox commentedI'm not using an overriding oa recent activity, so my export is the one that is in the codebase already
Comment #4
m.schwarzenberg commentedThank you for your answer, but I'm not sure if I have the original unmodificated view. In the first time several 500-Errors appears during saving the view.
I'm not able to get the original view from the original database without installing it again on a different location - Much effort for a 'perhaps' question.
Your export is that what I need.
Thanx in advance for your support,
Markus Schwarzenberg
Note: After last update with newest codebase the several error messages are gone...
Comment #5
Argus commentedYou can reset the view to it's original state on the Views overview page.
Comment #6
m.schwarzenberg commentedThank you.
I have reset the view and the error is still there. Additional I have restted the permission cache - no correction.
I have no further ideas.
But a useful hint is annexed as image: 'Action' strings like $USER was added to Group are visible!
I would reinstall openatrium completely but I have spent a lot of time to localize and customize it.
Comment #7
mpotter commentedAs hefox mentioned, the Recent Activity view is a view of Message entities and the output is controlled by the tokenized fields for each specific message type. If you look in your oa_messages submodule (within oa_core) you'll find the oa_messages.features.inc file that contains the default token fields. Here is an excerpt from the oa_update message:
You probably will just want to do grab the default version of this file from the code repo.
That is probably a very bad thing to do with an *Alpha* version of OA2. There are going to be a lot of bug fixes and improvements. You shouldn't be building real sites with the Alpha version yet. And if you are customizing it properly using your own modules and features, you should still be able to update the core modules. You don't need to reinstall completely, just grab the latest code.
Comment #8
mpotter commentedComment #9
m.schwarzenberg commentedThank you for the second explanation - Now I see clear what hefox mentioned.
My localization was via i10_module; Customization (only for own test purposes) was e.g. ckeditor as WYSIWYG UI and add/change mistranslated terms into german.
I can live with it if I had to reinstall it - but, as mentioned, updating to the latest code doesn't show any changes. Therefore I suppose problems in the database...
I will try on - Thank you for this great intranet solution!
Note: I'm working with OA 1 since 2010 for the different tasks and departments and to coordinate freelancer of my employer.
Comment #10
carlos.macao commentedI have the same problem and I also did some localization. I already reset the view, I compared the message_type table with a default one. Any suggestion?
Comment #11
m.schwarzenberg commentedWhich version?
I have had this problem with the .5 alpha release.
After completely new reinstall (data- and codebase --> but .3 - beta ) I have a working system. I have not localized it yet - But I do not suggest that this is the problem.
I have had 1-2 500' error during the install procedure.
To solve your problem I can annex a database dump of my present installation, if you have the beta .3 version. But not today.
Another hint: Connect your PC with a wire to your network instead of using WLAN when you install great software ditributions like this. This will decrease errors from exceeded response time.
Comment #12
carlos.macao commentedYes I've installed the last alpha version, just before beta release but I already updated to the last beta 3. Also, I've installed the beta into a new db and everything seems ok.
I can debug the process or compare the data of both installs to find the culpit, but I prefer not to waste time.
Comment #13
mpotter commentedcarlos.macao: Should not change the status of tickets from "cannot reproduce" unless you can post a specific step-by-step procedure for reproducing on a clean install.
Looks like a clean install fixed this for the OP, so closing it again.
Comment #14
carlos.macao commentedSorry. Any clue about the tables I should investigate?
Comment #15
m.schwarzenberg commented@ Mr. Potter - This should be only a hint for later reproducing
Not to forget - Addendum to #11:
I still haven't localize the installation, because there is an is an issue with localization.
@ carlos.macao:
Do you have localized your installation after the clean install?
Do not forget to safe your database before...
Comment #16
m.schwarzenberg commentedIn the meantime I have localized my installation - And..... the error is present again.
Error runs stable ;-))
I cannot define after which step of the localization the error appears again
- may be after adding the additional language,
- may be after setting german to new default language,
- may be after importing all module translations in stack
Is it necessary to modify the view 'recent_activity' for getting the right language?
Is it necessary to install entity_translation and entity_translation_views?
I hope that someone is able to see a way to remedy the fault with this additional hints.
@carlos.macao: New findings on this issue?
Comment #17
m.schwarzenberg commentedI have found the source of the error!
Clean install 7.x-2.0-beta4:
Only enabling 'Locale' module let the error appear - Disabling remedies it. I have not configured the module!
Also when I have configured it the error remains.
But how can I localize the site?
This leads the focus on the locale module, the preconfigured views or eventually an issue.
Edit: Tested on 2 different apache servers.
Comment #18
mpotter commentedThanks for tracking this down!
Yes, I can confirm that turning on the Locale module completely removes all of the existing token templates in the Message Types. You should probably post this over in the Message module issue queue since this is beyond Open Atrium.
The problem is that Locale is trying to create language-specific fields and is wiping out the default language fields. Not sure how Message will handle this to maintain it's settings when Locale is enabled.
Comment #19
m.schwarzenberg commentedThank you for bringing me on the next track....
Post it here: https://drupal.org/node/1935784#comment-7949317
Comment #20
m.schwarzenberg commentedSolved it: Hooray!!
Patch for entity on latest dev-release....
https://drupal.org/node/1782134#comment-7946243
Comment #21
giorgoskComment #21.0
giorgosktype error
Comment #21.1
m.schwarzenberg commentedPrecise information on issue
Comment #22
giorgoskok disregard previous
I was a little late at posting
Comment #23
mpotter commentedPlease don't change the Status to "Fixed" until this issue is fixed in OA2. We still need to apply the above patch to the Entity module in OA2 and by closing this it dropped off the issue queue so this didn't make it into the 2.0 release.
Comment #23.0
mpotter commentedh3
Comment #24
Argus commentedThe solution suggested in https://drupal.org/comment/8144727#comment-8144727 does
n'twork for me. (OA 7.x-2.09)edit: Ah wait: you select "language none" to your new language (Dutch in my case). That does the trick.
Comment #25
Argus commentedComment #26
Argus commentedComment #27
Argus commentedI think this is fixed.
Comment #28
Argus commentedRe opening because of #2171119: When enabling Locale Module "Recent Activity" View shows only empty rows
Comment #29
eigentor commentedI can confirm #20 that the patch linked fixes the issue. It is Entity module that needs to be patched.
Still Open Atrium needs to be fixed.
As long as there is no new release available for entity that contains the fix, maybe Open Atrium should be shipped with a patched Entity module?
Comment #30
mpotter commentedAdded the patch in #20 to the oa_core make file and updated to entity 1.3. Committed to bab0921 in oa_core dev.