Project

General

Profile

Actions

Bug #60713

closed

OAuth no longer works in 6.2

Added by Claus Harup over 9 years ago. Updated over 9 years ago.

Status:
Closed
Priority:
-- undefined --
Assignee:
-
Category:
-
Target version:
-
Start date:
2014-08-01
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
5.5
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

I have had the following running smoothly in TYPO3 6.0 and 6.1:

include_once 'HTTP/OAuth/Consumer.php';
require_once 'HTTP/OAuth.php';
require_once 'HTTP/OAuth/Consumer/Request.php';
require_once 'HTTP/Request2.php';

// Set up HTTP request
$httpRequest = new HTTP_Request2;
$httpRequest->setHeader('Accept-Encoding', '.*');

// Set up OAuth consumer
$request = new HTTP_OAuth_Consumer_Request;
$request->accept($httpRequest);
$consumer = new HTTP_OAuth_Consumer($consumer_key, $consumer_secret, $access_token, $access_secret);
$consumer->accept($request);

.... but after upgrading to TYPO3 6.2 it fails on all the include and require parts above!?!?

Actions #1

Updated by Markus Klein over 9 years ago

  • Status changed from New to Needs Feedback

I guess TYPO3 already loads these libraries by default. Did you try removing these lines?

Actions #2

Updated by Claus Harup over 9 years ago

Yes I did but then:

// Set up HTTP request
$httpRequest = new HTTP_Request2;
$httpRequest->setHeader('Accept-Encoding', '.*');

// Set up OAuth consumer
$request = new HTTP_OAuth_Consumer_Request;
$request->accept($httpRequest);
$consumer = new HTTP_OAuth_Consumer($consumer_key, $consumer_secret, $access_token, $access_secret);
$consumer->accept($request);

crashed!

I set it up in Classes/Utility - should I do it differently?

Actions #3

Updated by Markus Klein over 9 years ago

"it crashed" does not say too much.

What is the error message?
Does the class, the code is in, use namespaces?

Actions #4

Updated by Alexander Opitz over 9 years ago

  • Status changed from Needs Feedback to Closed

No feedback within the last 90 days => closing this issue.

If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.

Actions

Also available in: Atom PDF