Hi, Everyone:
I made the suggested change from http to https, but I still have failure in
connecting to Creative Commons. I restarted tomcat and cleared the cocoon
cache, as well.
George Kozak
Cornell University
On Mon, Apr 2, 2018 at 7:59 PM, Javier Távara wrote:
> Thank you for the update Rob
Heya Javier.
Thank you for checking this.
There is a 301 redirect in place from http to https.
The old server had Varnish publicly accessible on port 80, which I assumed
was an error so I didn't recreate that (we were meant to have switched
everything to https a couple of years ago!).
If chan
Thank you for the update Rob.
Any redirection is being applied from non-SSL to SSL? Was the same before
the update?
I changed my settings (dspace.cfg) to use SSL:
# The url to the web service API
cc.api.rooturl = https://api.creativecommons.org/rest/1.5
And it works now :)
- Javier.
El lunes
Heya everyone, Rob from Creative Commons here.
I'm very sorry that our API isn't working with DSpace at the moment. I
upgraded the server that the API runs on, and the problem that you are
seeing wasn't caught by my tests.
If I call the API simply via the command line, e.g.:
curl -d
"answers=
I saw the tweets. Thank you.
As we don't have any useful logs of what's happening, I thought
disabling/enabling the step could fire any sort of cache clearing.
No success.
- Javier
El lunes, 2 de abril de 2018, 17:33:16 (UTC-5), Keith Gilbertson escribió:
>
>
>
> On Monday, April 2, 2018 at 6:
On Monday, April 2, 2018 at 6:18:47 PM UTC-4, Javier Távara wrote:
>
> I really don't want to disable the CC License step.
>
> That's understandable. Our repository team has been encouraging people to
select CC licenses.
Rob Myers at Creative Commons is aware that some DSpace repositories have
I really don't want to disable the CC License step.
Disabling/enabling fixes nothing by the way.
- Javier.
El lunes, 2 de abril de 2018, 16:43:29 (UTC-5), Keith Gilbertson escribió:
>
> George, we've had similar problems today. We'll probably disable CC
> License steps for now, and then restart
George, we've had similar problems today. We'll probably disable CC License
steps for now, and then restart Tomcat. On our system, this is configured
in /dspace/conf/item-submission.xml
--keith
On Monday, April 2, 2018 at 5:31:29 PM UTC-4, George Kozak wrote:
>
> Hi,
> We have a DSpace 5.5 and a
Hi -
We experienced some problems with submissions at Virginia Tech today
(DSpace 5.X, XMLUI, Creative Commons License Enabled, item-submission.xml
style submission process). The submissions failed just before the Creative
Commons License step. I don't have a stack trace because our system was
Our DSpace instances are in the same situation. Like you said, the CC
Twitter account says the API is back up, but we still get a
NullPointerException when contacting it.
On Monday, April 2, 2018 at 4:31:29 PM UTC-5, George Kozak wrote:
>
> Hi,
> We have a DSpace 5.5 and a DSpace 6.2 install.
Hi,
We have a DSpace 5.5 and a DSpace 6.2 install. This afternoon, the CC
License submission step stopped working and caused an internal error. I
don't use Twitter, but one of my co-workers who does saw Creative Commons
tweeted that their API was broken, but an hour later said it was back up.
How
Hi Tom,
Sorry for late reply. Somehow I missed your posting and just found it by
doing a search.
"would it be possible for any of you to provide an anonymised and cleaned
database that you can share with us? Make sure the database does not
contain any sensitive information. I'm sure such a databa
Hi everybody,
We have got several items in first step from workflow. We need a backup to
this items before delete them. Is there some command line to do this task?
Is there some command line to delete items massively from workflow?
Many thanks.
Walter Blandón
--
You received this message be
13 matches
Mail list logo
