SonarQube: Issues for one project are not displayed - sonarqube

In my SonarQube installation for one project the issues overview can't be displayed, it always shows "Still working..." at the top.
See http://didge.my-wan.de/sonar/component_issues/index?id=net.troja.eve%3Aproducersaid
When I navigate to the files directly I can see all the issues! Only the overview doesn't work.
Any suggestions?
PS: I change to logging to debug, but couldn't find anything useful.

It looks like a string escaping bug. If you rename your project to remove the quote character, the page will display correctly. I have created a JIRA issue to track this, will be fixed in 5.2 (and maybe backported to 5.1.x).

Related

Joomla error "MODULO BY ZERO"

This error showed up as plain text on white background after logging in to the Maintenance Login window on the public front end of our Joomla 3.5.1 site. We are using a template from TemplateMonster called "theme3289" (default version), aka "Truckie".
For no apparent reason, we found we could not log in to the Maintenance Login window on the public front end. We got the error:
"Modulo by zero" on a plain white background.
No part of the front public end of the site could be navigated to, even by pasting in a link. However, we could navigate fine to the backend ([site_domain_name.com]/administrator)
Not sure exactly what caused this, but we did have the internet connection go down in the middle of saving an article. After re-gaining connection, the new article was missing. We had also made some simple content changes (not configuration or settings changes) in the articles inside the TM Parallax module.
Looking for help on this "Modulo by zero" error.
RESTORED DATABASE BACKUP = Solved the problem. I am pretty sure it was some kind of database error or corruption. We tried clearing the cache (Joomla System Menu) and a number of other things. Nothing worked.
We had two staff working on the site at the time of the error, one a newbie, one an advanced beginner. Interviewing them with "what were you doing at the time" didn't seem to lend any clues. Unless perhaps the TM Parallax module may have a bug (???) - or a corruption somehow when internet went down while saving an article.
SOLUTION: We restored a recent backup copy of the database made only 2 hours prior to the ERROR. This solved our problem.
This worked for us.
I faced this issue today, and I found out the cause. Its simple actually,as the issue says your code somewhere is attempting to do division or modulo by 0. Maybe you had added a new field with value 0 in your db after taking backup and the data there was causing it. This may not be helpful for you now but I'm leaving this here to make it easy if someone has a similar issue and ends up here.
I think the problem was caused by a change in the template. For example, some templates do not allow specific values to be zero, and will crash when this happens.
A good idea to discover the root cause of the problem is to compare the templates settings of the backup to the template settings of the problematic site. If everything is exactly the same, then you should compare the modules, and finally the menu items. It is not a fun job to do, but will help you isolate the problem in case it happens again.
For your reference. Just had this issue and the above information did not help. Finally found the solution:
In Article > global Options > Blog/Featured layout I had the columns set to 0

What is the right-side white area of XCode editor?

Does anyone know why?
EDIT
I've found it. It was a page guide.
After i unchecked it, it disappeared
This looks like a bug to me.
What have you selected to get this?
Is this behavior all the time or you get rid of it when you restart or build your project?
If it happens to be a bug I would recommend you to report a bug to Apple.

Wrong URL used when accessing article through a module

I have an annoying problem and am hoping someone will be able to help.
We use quite a few extensions on our Joomla site (Roksprocket mainly but also Global News Filter for instance).
The modules themselves are working fine however when I click on an article in one of these modules the article opens but it doesn't use the nice URL that should be displayed (we have Search Engine Friendly URLs set to Yes and Use URL rewriting set to Yes). This happens for all modules that draw off a category (so I don't think its linked to a specific extension).
For instance on our Case Studies page if you click on Read More on the RSA Case Study you get this URL
http://www.assima.net/en/resources/case-studies/99-home/resources/case-studies/ats-case-studies/649-case-study-rsa
but what you should get is the menu item URL associated with this article which is this
http://www.assima.net/en/resources/case-studies/ats-case-studies/rsa
I don't think there is anything wrong with our .htaccess as I reverted back to the default Joomla one and it still occured.
Also this used to work perfectly. I first noticed it around October or November last year.
If anyone has any ideas I would really appreciate it, I've googled the problem many times and not found any help.
Thanks
Emma
FIXED.
Due to a Joomla bug. Fixed by overwriting the route.php file as described in this post: http://forum.joomla.org/viewtopic.php?f=625&t=831007&start=30

Layout corrupted in ADF projects

I'm working on some projects on Jdeveloper 11.1.1.2.0 IDE and encounter an annoying problems. The layout of jspx pages corrupted, all control attached to any page disappear without a trace when running project. They dont show in design tab either. The problem appears suddenly when I modify some page.
Now I cant working on the project and have to restart project from scratch. So if you have encountered and fixed the same problem. Could you please show me how to do it. I'm very grateful to hear any suggestion.
Thank you.
Your description doesn't allow any educated guess on what happens. Can you at least paste the page source that you encounter the problem with ?
Often issues like this occur by developers placing the content to a facet that is not made for this and that does not stretch. Or if the a tag is not closed properly or missing (the page source editor should flag this)
Before starting from scratch, which should not bee needed at all, try JDeveloper 11.1.2.2 to reproduce it in a later build.

WYSIWYG buttons don't show in IE for CKEditor

I have a fresh installation of Liferay on Tomcat and in IE7 it doesn't show the buttons for visual editing in the editor when I try to edit content.
It works on in Firefox or Chrome.
Does anyone have an idea why would that happen? I am not sure where to dig, I don't see javascript exceptions and it doesn't look like the buttons are even populated in IE. It is hard to debug IE problems since I don't have a tool like Firebug there.
I downloaded the 6.1 and still have the same problem, adding the URLs of what I see. Looks like IE only has the text box and in the DOM I don't see the same things that I see in FF.
http://i44.tinypic.com/35jf5td.jpg
http://i43.tinypic.com/11qqvt0.jpg
Update on this:
I checked with some people in our organization and they have the buttons on their browser.
I checked the version of the IE browser and it's the same down to the last digit. Properties are the same as well. The only difference is that I have some plugins installed that the other browser doesn't. I tried disabling all the plugins but it didn't help.
The suspect plugin is Google Chrome Frame (ChromeFrame BHO). Can someone please try to add this plugin and see if it messes things up? The disabling it doesn't help.
Liferay CE 6.0 contains few bugs within the WYSIWYG editor integration.
One issue with IE is LPS-16004 (solution included). This might be the same problem as you are experiencing.
I remember we had also problem with javascript race condition in editor initialization, which sometimes loads the editor incorrectly.
But I strongly suggest you to move to Liferay CE 6.1 as it is much more stable.
Ok, I finally figured it out, so if someone has the same problem, here is the reason - we have Google Chrome Frame plugin installed in our organization, but it only works on white-listed domain names. In this case the domain the site was on wasn't whitelisted, but the portal looked at the agent string and saw chromeframe there and assumed it can use it as chrome browser, which broke things.
Right now I will try to white-list the domain and see if it works. Another solution would be to try and find a place where we look for the agent string and fix it there, not sure where this place is.

Resources