#2071: Use the month on the sopnsors page
---------------------------+-------------------------------------
Reporter: cvvergara | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: Systems Admin | Keywords:
---------------------------+-------------------------------------
The sponsor to be showed on sponsors page is done automatically based on
the year.
When the year changed the sponsor were move to the section past sponsors.
The query should be done based on month and year.
The month and year are the "up to what date the sponsor should be shown
(Including)
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2071: Use the month on the sopnsors page
---------------------------+--------------------------------------
Reporter: cvvergara | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website rebranding 2017
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+--------------------------------------
Comment (by cvvergara):
General idea of where changes need to be done:
File where the change needs to take place:
https://git.osgeo.org/gitea/osgeo/wordpress/src/branch/master/wp-
content/themes/roots/archive-sponsor.php
This template is called
https://git.osgeo.org/gitea/osgeo/wordpress/src/branch/master/wp-
content/themes/roots/templates/atomic/organism-sponsors.php
As the year just changed, and its not a blocker I want to change the
milestone for after the site is published
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071#comment:1>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2071: Use the month on the sopnsors page
---------------------------+---------------------------
Reporter: cvvergara | Owner: sac@…
Type: task | Status: new
Priority: normal | Milestone: Website v2.1
Component: Systems Admin | Resolution:
Keywords: |
---------------------------+---------------------------
Changes (by cvvergara):
* milestone: Website rebranding 2017 => Website v2.1
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071#comment:2>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2071: Use the month on the sopnsors page
-----------------------+---------------------------
Reporter: cvvergara | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website v2.1
Component: WebSite | Resolution:
Keywords: |
-----------------------+---------------------------
Changes (by cvvergara):
* owner: sac@… => webcom@…
* component: Systems Admin => WebSite
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071#comment:3>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2071: Use the month on the sopnsors page
-----------------------+---------------------------
Reporter: cvvergara | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website v2.1
Component: WebSite | Resolution:
Keywords: |
-----------------------+---------------------------
Comment (by jive):
Replying to [comment:1 cvvergara]:
> File where the change needs to take place:
>
> https://git.osgeo.org/gitea/osgeo/wordpress/src/branch/master/wp-
content/themes/roots/archive-sponsor.php
>
> This template is called
>
> https://git.osgeo.org/gitea/osgeo/wordpress/src/branch/master/wp-
content/themes/roots/templates/atomic/organism-sponsors.php
>
> As the year just changed, and its not a blocker I want to change the
milestone for after the site is published
Can we work on this now? See #2158 it is become a live issue for me (can
no longer see GeoSolutions sponsorship logo for example).
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071#comment:4>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2071: Use the month on the sopnsors page
-----------------------+---------------------------
Reporter: cvvergara | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website v2.1
Component: WebSite | Resolution:
Keywords: |
-----------------------+---------------------------
Comment (by robe):
Before we start working on this let me correctly set up the staging, prod
branches on gitea and have pull from respective like I did for FOSS4G
2018.
I'll get to doing this in the next day or 2.
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071#comment:5>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.
#2071: Use the month on the sopnsors page
-----------------------+---------------------------
Reporter: cvvergara | Owner: webcom@…
Type: task | Status: new
Priority: normal | Milestone: Website v2.1
Component: WebSite | Resolution:
Keywords: |
-----------------------+---------------------------
Comment (by robe):
I have now split branches into staging and master, master is production.
The server will push to each respective site as detailed in readme.
Note also I renamed the repo to www_osgeo (since wordpress was too generic
and we have other wordpress sites now).
https://git.osgeo.org/gitea/osgeo/www_osgeo
I've also refreshed the staging database so it's ready for testing these
fixes and others and hopefully should mirror production issues.
One thing I also did was upgrade gravity forms on staging (the message
about upgrade was a bit scary, so before I upgrade it on production, I
wanted you to all take a see an make sure no surprises there).
--
Ticket URL: <https://trac.osgeo.org/osgeo/ticket/2071#comment:6>
OSGeo <http://www.osgeo.org/>
OSGeo committee and general foundation issue tracker.