Vouchers on Drupal (3)

We care for the deveoplment of a Drupal website that sells vouchers and coupons. For adding some features and fixing bugs, we need more development capacity. The site already exists: [login to view URL] It is highly enhanced with modules and multi-domain-configurations. Most of its data is fetched from external JSON streams, and not in the local database (this is done by a self-written module). As the site is German, it might be an advantage if you can read the German language, but it might not be necessary. We provide you a cloud9 workspace where everythin is set up so you can start coding right away. It would be great if you have or can create a free (!) user account at cloud9: [login to view URL] (If it's not possible for you because of credit card, please tell us - we will try to help you out.) We seek for a long-term development realtionship with a real Drupal expert. This project is set up to provide you two tasks where you can show your experience and abilities. Please make a rough estimation on how many hours you think it might take for the given two tasks. Please also tell us how much you will take per hour in general (we will pay per hour), and the total estimated price for the two tickets. Here are the respective example tickets/tasks: Ticket 1#: Our blog's pager does not work any more We have created our own blog functionality in Drupal. Not very well implemented maybe, we have some module dependencies. Such a deppency seems to have broken our blog pager. It does not work any more. You only see the first page of a category, but you cannot see the older pages. This must be fixed - without destroing the other blog functionality :-) Ticket 2#: When a new front page forwarding is set, web browsers should load the new forwarding after a few seconds Currently, Drupal sends 301 forwardings for the frontpage: Request URL:[login to view URL] Request Method:GET Status Code:301 Moved Permanently (from disk cache) Remote Address:[login to view URL] Referrer Policy:no-referrer-when-downgrade Response Headers Cache-Control:public Content-Length:0 Content-Type:text/html; charset=UTF-8 Date:Tue, 25 Apr 2017 14:54:24 GMT Expires: Location:[login to view URL] Server:nginx/1.6.2 X-Content-Type-Options:nosniff Look here: [login to view URL] That causes web browsers to cache the front page forwarding almost endlessly... Instead, browsers should accept a new forwarding of the fronpage within seconds. You mighht try replace the 301 forwarding on frontpage by a 302 forwarding