ladiaria / utopia-cms Goto Github PK

Utopía is an open source platform for community based newsrooms to manage their subscriptions. Code repository for the CMS tool.

License: BSD 3-Clause "New" or "Revised" License

Shell 0.13% Python 57.35% HTML 26.22% JavaScript 5.88% CSS 1.27% PHP 0.13% SCSS 9.02%

cms journalism latinoamerica media spanish uruguay

utopia-cms's People

Contributors

Stargazers

Watchers

Forkers

hernan0216 djpeluca cumanachao emiliodelgadouy artis-physis gonzaddv

utopia-cms's Issues

Fork tagging_autocomplete_taggit and change it to support Django 1.11

At least the "json" import in views should be hanged

Ads in non-default publication's home

Write a new template tag to check if the user is subscribed to publication
Use it to render (or not) the html container in portal/teplates/cover.html (line19 section id=header-pub)
Load the ad using js at the end of portal/teplates/index_pubs.html (analog to portal/teplates/index.html)

filters by agency and photographer

the "TODO" in photologue_ladiaria/admin.py

filter by subscribed in /admin/thedaily/subscriber

thedaily.views.registered_users loads data from a migrated custom command, decide what to do with this view / the related command

Update a changelog de release 0.0.2

En el release https://github.com/ladiaria/utopia-cms/releases/tag/0.0.2

Agregar al changelog https://github.com/ladiaria/utopia-cms/blob/main/CHANGELOG.md

En el bullet del feature "Lista de lectura", este texto "Feature details at https://ayuda.ladiaria.com.uy/que-es-la-lista-de-lectura/ (Spanish)"

Installation document for LightGallery is wrong when pulling from main branch

Describe the bug
When pulling the LightGallery module during the installation process documented in the file INSTALL.md is requesting to do that from main branch which does not exist. Related with this issue: ladiaria/lightGallery#1

To Reproduce
Steps to reproduce the behavior:

Clone the LightGallery repository as documented:
user@host:~/utopia-cms $ git clone -b main https://github.com/ladiaria/lightGallery static/lightGallery
Error message states that main branch does not exist.

Expected behavior
master branch in LightGallery should be renamed to main.

Desktop (please complete the following information):
N/A

Smartphone (please complete the following information):
N/A

Additional context
ladiaria/lightGallery#1

Minimum version of mariadb required

Check the minimum version needed of mariadb, (10.5.1 is ok)

signup with a category

In ladiaria we have a signup version that automatically adds a category (previously selected by the user navigation flow) to the subscriber's category newsletters, verify if this feature can be included in utopia

improve rendering of live embed events notifications

This notifications are rendered now using a template tag, which can let to render them over other alerts (breaking news & mobile subscribe-notice).

The template tag approach should be migrated to an ajax approach (like breaking news does), the priority to consider to render the alerts then, should be:

breaking news
live embed events (this)
other custom alerts from other apps (implemented overriding the needed js blocks in this apps, not here)
mobile subscribe-notice

Satirical sections by settings

The article's detail page "@type" meta tag is rendered with "SatiricalArticle" value if the section slug is in this new setting. (Now this is hardcoded to "humor" section)

Error trying to delete a "followed" article

To fix, I will implement this solution: justquick/django-activity-stream#48 (comment)

check install and upgrade procedures from scratch

Check usage of core_tags.send_by_email_form

Is probably not used anywhere, if so, remove it and all its related classes/templates/views/urls

subscribe CTA popups should be optional by settings

And also a text label for the desktop version is taken from the default pub, it should be changed also to be taken from a better source (a setting seems to be the best option)

Update AUTHORS.md including people who have contributed in the past

Ignacio Toledo
José Callero
Bruno Sarlo
Miguel Lezama
Guillermo Colmenero
Alvaro Mouriño
Eduardo Roldán
Diego García

Photo slug does not change automatically

Try to edit a photo and change its title in /admin/photologue/photo (slug should be updated, and seems not)

core.models.update_category_home improvements

There is a comment in the function that says to improve the stop condition when there are fixed articles (for this categories, the needed value would be less than the hardcoded value of 10).

DONE iterate over ArticleRel.edition.date_published ranges, this way, in a very populated environment (the most probable scenario) we can achieve goals in the first range iteration, that would be much faster than execute the whole join with no date restriction.

DONE Another improvement: the most inner for iterates over all categories, this can be easily improved into an iteration over only those categories that need more articles, pseudo:

categories_to_fill = settings.CORE...

if categories_to_fill:
    ...
    for edition in ...
        for ar in ...      
            if categories_to_fill:
                article = ...
                for cat in categories_to_fill:
                    if article matches criteria to enter:
                        append the article
                    if now this cat is full:
                        remove it from the categories_to_fill list
            else:
                stop = True
                break
    if stop:
        break

DONE But also there is another good thing to do there: when the home is not fully-filled, is much probable that there aren't more articles than this number, so, we can previously count them (new Category method) to know which is the new max value and also decrease the "needed" value to this counter (in a per-category way), this avoids the unnecessary loop until the oldest edition that will not find anything.

Of course this improvements not cover all the scenarios that can run the "complete" loop, but minimizes them in a very good way.

DONE important PD: the hardcoded value "11" should also be reviewed, because we need 10, the value is used to iterate over a range that could be easily fixed later with a simple "+1". check, fix and test this improvement before doing anything else.

NameError at /usuarios/restablecer/

trying to reset pass using a non-logged-in session

portal/apps/thedaily/views.py in password_reset
                    u'Recuperación de contraseña', user, 'notifications/password_reset_body.html', 

global name 'user' is not defined

app_label in core.models

How it works? (seems that comparison with "core" is wrong)

custom "datos" article in newsletter NL preview/send

"datos" should be a setting

pending de-customizations

grep -ni "la diaria" --exclude={"*.md","*.*css*","*.less","*.svg","*.lock","logo.html"} --exclude-dir={vendor,locale} -Ir .

Create the branch for the future release for Django 1.11

The install guide should include the steps to generate and migrate the tables for social_django, we already have a procedure to upgrade this app from Django 1.5.

css fixes in the AMP version of article detail template

article photo centered
other things: share links, paywall div components (buttons)
may be more things

is_subscriber perms should be managed more wisely

There's no warning to the user to add or modify a permission when a publication is added or modified its slug, the permission is needed to check if a user is subscribed to the publication.

This way of checking is complicated to maintain, because to fix it, we have to modify the Publication save method or make triggers to handle the permissions involved with the addition or modification that was made.

We have to think another easier way to manage this subscriber permission related to a publication, a group related to the publication can be an option, this approach is already used someway in another thedaily model.