#4 — Caching problem
by
Ralph Jacobs
—
last modified
Jul 15, 2011 03:28 PM
| State | Resolved |
|---|---|
| Version: | 0.4 |
| Area | Functionality |
| Issue type | Bug |
| Severity | Medium |
| Submitted by | Ralph Jacobs |
| Submitted on | May 30, 2011 |
| Responsible | Ralph Jacobs |
| Target release: | 0.4 |
In twitter.py I had to change the Cache paremter from DEFAULT_CACHE to None for the portlet to run (and allow Plone to run):
def __init__(self,
username=None,
password=None,
input_encoding=None,
request_headers=None,
cache=None):
I think this should be exposed to the site integartor so that such a small thing as twitter caching doesn't brake the whole site.
Here's a link to the solution:
http://code.google.com/p/python-twitter/issues/detail?id=59
def __init__(self,
username=None,
password=None,
input_encoding=None,
request_headers=None,
cache=None):
I think this should be exposed to the site integartor so that such a small thing as twitter caching doesn't brake the whole site.
Here's a link to the solution:
http://code.google.com/p/python-twitter/issues/detail?id=59
Added by
Ralph Jacobs
on
Jun 03, 2011 03:17 PM
Issue state:
Unconfirmed
→
Confirmed
Added by
Ralph Jacobs
on
Jun 03, 2011 03:18 PM
This will be fixed in 0.5
Added by
Ralph Jacobs
on
Jul 15, 2011 03:28 PM
Can't reproduce this anymore in 0.5, closing the ticket.
Issue state:
Confirmed
→
Resolved
No responses can be added.
If you can, please log in before submitting a reaction.
