Support

    You are here:  
  1. Home
  2. Support
  3. Image crop size applied the same for all image fields and e-mail weird validation
Toggle Submenu
  1. Forums
  2. Recent
  3. Categories
  4. Tags
  5. Users
  6. Badges
Support is currently Offline
Support Offline
It's past support hour. We are taking some rest and will come back stronger tomorrow. Promise!
Official support hours:
Monday To Friday except Saturday and Sunday
From 09:30 To 17:00
Our current time: Friday 5:10 am
Add a reply View Replies (6)

Resolved Some possible bugs in the Social Plugin

  1. zuotoski
    zuotoski
  2. Bug Report
  3. Friday, May 09 2014, 06:12 AM
Hello,

Some possible bugs that I've found today:

- Wrong accents visualization in the "Post View" - like ç , Ç, ã, õ, For example: the word ACENTUAÇÃO is displayed like this: ACENTUAÇÃO

- If the user logs in the backed, the status is displayed as online in the Social FrontEnd, even if the user is logged off the frontend.

- There is a little problem with the menu, if the words of the menu items are longer than the default (when I say default I mean English) it breaks to the next line - see the screenshot. I guess that it will be solved when the new CSS template is ready (please forgive me if I am wrong).

Regards.
Attachments (1)
menu_break_line.png menu_break_line.png
Responses (6)
admin
admin Accepted Answer
Admin
Good! very thanks for your help ;)
  1. more than a month ago
  2. Bug Report
  3. # 1
admin
admin Accepted Answer
Admin
There is a little problem with the menu, if the words of the menu items are longer than the default (when I say default I mean English) it breaks to the next line - see the screenshot. I guess that it will be solved when the new CSS template is ready (please forgive me if I am wrong).


I have investigated, please remove from your override.css these:
remove !important from line 302,303,305
remove line 137,138,139
  1. more than a month ago
  2. Bug Report
  3. # 2
zuotoski
zuotoski Accepted Answer
Content Protected
  1. more than a month ago
  2. Bug Report
  3. # 3
admin
admin Accepted Answer
Admin
Ok, I understand.
I think you should do so:
- Disable 'Include Bootstrap CSS files'
- Remove your directive in override.css to resolve conflict with bootstrap CSS
- add at the start* of override.css the code attached to this post, this contains only bootstrap classes for tabs,button,dropdown button (used for privacy) and icons (used for privacy and some field).

* You can add everywhere you want, but the directive @import must be at the top of file

Do a backup of your override.css before.
Attachments (1)
bootstrapsomeclass.txt
  1. more than a month ago
  2. Bug Report
  3. # 4
zuotoski
zuotoski Accepted Answer
Great!

I'll send you a PM about a special request. Well, I was testing the new layout, but at the same time I've added new fields and now I have error 500 in the frontend and in the backend i have a "String could not be parsed as XML".
I tried to identify what is the problem by turning on error logs and system debug with no luck,

Just to aknowledge you, this error has nothing to do with the CSS that you've sent, I am aware of it.

EDIT: It is just happening to the existent users, if I try to create a new one, there is no error. I didn't create any new user to test, just entered in NEW to see what would happen and cancelled without doing anything.

Sorry for that.
  1. more than a month ago
  2. Bug Report
  3. # 5
admin
admin Accepted Answer
Admin
Ok, this is a bug. this heppen when there are char " in default value.

we will fix in next release
  1. more than a month ago
  2. Bug Report
  3. # 6
  • Page :
  • 1


There are no replies made for this post yet.
However, you are not allowed to reply to this post.
Sorry, the discussion is currently locked. You will not be able to post a reply at the moment.

Request Support

Support is currently Offline
Ask a Question
Official support hours:
Monday To Friday except Saturday and Sunday
From 09:30 To 17:00

Support Availability

Working days: Monday to Friday. The support staff is not available on weekends; in the most of cases tickets will not be answered during that time.

Reply time: Depending on the complexity of your support issue it's usually between a few minutes and 24 hours for paid members and about one week for free members. When we expect longer delays we will notify you.

Guidelines

Before you post: read the documentation and search the forums for an answer to your question.

When you post: include Site Details if you request a support (you can use the form below the reply in Site Details tab).

Auto Solved Question: If after a week the author of the post does not reply to a request by moderator, the question will be marked as resolved.

Language: only English

Search Users

Easy Profile® is not affiliated with or endorsed by Open Source Matters or the Joomla Project. Joomla is Free Software released under the GNU/GPL License.

We use a few cookies

Our site uses non fat, delicious cookies which help us improve your user experience. You can read more about it in our Legal page.