isamuni / isamuni Goto Github PK

Having set datatables for the events table, I am now unable to use typeahead.
I am actually thinking whether it is worth removing typeahead at all (it looks great though!)

See commit: 3544a45181df3d6d69a864bcbef1f882bb438d42

page_path(page) does not work properly within the /admin portal.

Current hack:

        <!-- This is a dirty hack to get the page path correctly. Please FIX -->
        <% if page.community? %>
          <% kind = 'communities' %>
        <% else %>
          <% kind = 'companies' %>
        <% end %>
        <%= link_to kind + '/' + page.slug, class: "btn btn-primary btn-xs" do %>
          <i class="fa fa-eye"></i>
        <% end %>

How to reproduce the error:

1. go to one of the pages with a search bar
2. click on a link (e.g. a user)
3. hit the back button on your browser
4. repeat 1-3

The navbar should look weird (an overgrown navar :P)

This issue might be related with the typeahead search bar. We want to move it outside of the navbar anyway, so that might solve it.

Adding it to the Title of each page seems to be the easiest and most logical thing

Should be able to remove users or temporarily ban them

Some events may not be organised by groups/pages, but by users of the system.
Users should be given the possibility to add events manually.

have button/option to let users reset zoom and location of map

How to reproduce:

1. expand upcoming, future tables
2. collapse them
3. then click on any event in the map and expand it

You should see the future and upcoming tables overlapping.

• http://guides.rubyonrails.org/security.html
• https://www.owasp.org/index.php/Ruby_on_Rails_Cheatsheet

Get profile picture from fb for the pages and use it the same way we do it for users.

Create a test page.
Go to http://squirrels.vii.ovh:3000/me/pages
Attempt actions.

Routing issues should arise.

We need a first real or real-looking company into the database, so that we can focus on making it look as good as possible, and use it as a showcase for what our website can do.

if post or events has been updated since last crawl, then update entry in DB

There will be two events endpoints

GET /events

return the latest X events

GET /events/page (e.g. page=1)

Will return events from oldest to new. This way we avoid having inconsistencies in the results.
RESPONSE (example):

200 OK HTTP/1.1

[
  {
    event1
  },
  {
    event2
  }, 
 ....
 {
   next:   /events/2
 }
]

Date picker in the community feed does not work properly when the slider is used.

Not sure there is a fix.

https://developers.facebook.com/docs/plugins/page-plugin/

use fb_id as taken from the user input

The interactions between the map, the search box and the timeline are currently unclear. We should make things look simple (for example renouncing at the timeline-map association, and then moving them to different parts of the page to make it clear they are distinct).

Future events: display day/month (year is assumed)

Old events: display day/month/year

Lets assume we have a page P owned by a user U.
All posts of U containing a set of tags T should be associated with P. So, when other users look at P, they should see some related posts.

number employees is shown when creating a page, whether is a community or not.

disable field if community.

Some posts have a job tag, but are not job offers or job related. Admin should be able to change the category for such posts.

Need to check user permission on admin_controller

Adding tags to the profile model would provide useful information at a glance directly from the list of all users, and would be useful for searching / displaying the most common skilss etcetera
example:
"foto | Gabriele Viglianisi | Studente al polimi | nodejs, rails, c++, exploiting"

Suggested by @giupardeb

http://seotesteronline.com/ is a good tool :)

Leaflet markers overlap if two events happen in the same location. See image below for events of 24th and 25th October.

A registration page is needed. This action should be distinguished from the basic login action.

On the registration page, we should make clear what data we crawl from FB.

The idea is basically passing a date range as a query to the community_feed page and use that for filtering.
/community_feed?start=2016-04-01&end=2016-10-01
then the user could use the date picker as he is doing now, but he would have to press a button to reload the page with different query parameters

pros:

• No needs of ajax, simpler code, single endpoint
• It is easy to add other parameters (eg) a search filter on the content or on the kind of post, just add them to the form
• we'd obtain a bookmarkable search
• would look better, because the user doesn't see a the content changing "live" on the page... in theory this shouldn't be a problem, but we don't have any loading indicator, so the user doesn't even know if the new content has been loaded or not.

cons:

• ajax is already implemented

Update event tables based on time selection from the google chart time slider.

• There should be a string displaying the current search parameters
• The range selector should reflect the current query

Needed for Opendata requirement

Self-explanatory...

• location
• lookingfor
• sector

Use a configuration file to specify the groups to crawl. This will make the crawler more feasible and easy to maintain

I disabled the page's map for v0.1.
While this feature will be very useful and awesome, I think we can delay it a little bit.

Moving this requirement to v0.2.

Current view:

1    4   7
2   5   8
3   6   9

This makes it hard to follow posts in a temporal order.
Ideally, we would like to have them ordered as:

1   2   3
4   5   6
7   8   9

This cannot be achieved using column-cards from Bootstrap 4. We could have a grid of cards, but spacing would be terrible + all cards will have to be of the same height.

I tried Masonry, but (1) it does not work very well, (2) it looked slow.

Any ideas? Do we actually even care about the order?

A page owner might add a FB page (or multiple?) to the page.
The result would be that posts from that page are crawled and displayed on the page.

Option: the user specified a set of tags, so that only posts with those tags are crawled

This could also be extended to Twitter accounts

display events on the map as ongoing based on the date range (start and end date), rather than based on start date only

Currently using POST.

Should use PUT which is idempotent.

The event page needs a new layout
Problems:

• Events are classified as "past, current, ad upcoming", but on the interface they are only distinguished by their color. They should be labeled somehow.
• MOVED to #35 - The interactions between the map, the search box and the timeline are currently unclear. We should make things look simple (for example renouncing at the timeline-map association, and then moving them to different parts of the page to make it clear they are distinct).
• The map loads after the page, the rest of the page (the list of events), there's an ugly white box in the meantime
• The map is so big that the user has to scroll to see the list of posts. In theory the posts should be immediately visible. Moving the map to a sidebar may be a good idea, as it is not the main source of information on the page, at least for the time being.

Ideas: we could move the upcoming events up in the page, so that they are immediately visible. Then the others could go further down in the page, or even in a separate one.

This could be achieved using OpenStreetMaps.
Leaflet.js seems a good option. There is also a gem for it: https://github.com/axyjo/leaflet-rails

How to get a location, given an address: http://wiki.openstreetmap.org/wiki/Nominatim

see: http://guides.rubyonrails.org/i18n.html

How to reproduce:

1. Go to any other page other than the home page
2. Go back to the homepage via the 'ISAMUNI' link (top-left)

Output: no google chart

I believe the problem is that we are just making the @posts and @post_jobs objects on home#index (controller) and not invoking any js of that page.

this operation can be done when creating the page.

As of today, this can be easily done for groups. Just have graph.facebook.com/ID-GROUP/admins and check that user is in the list.

However, the same api is not available for pages. We could, however, get the list of pages a user is admin of. In that case we will have to request some permission from the user on login.

Admin should be able to remove posts

Very basic question, but fundamental.

If we want to avoid having people from outside (especially from outside Sicily or any region if we think about the long-term plans) then we should check whether the user is a member of the PAC group.

A problem with having users from outside is that the admin work is going to increase (banning, etc).

An advantage with having users from outside, on the other hand, is that we gain visibility.

active/deactivate buttons are not using the bootstrap styles