Hello,

I get the following error in my logs:

You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DESC LIMIT 0, 5' at line 1 query: SELECT node.nid, value, node.title AS node_title, node.changed AS node_changed, users.name AS users_name, users.uid AS users_uid, votingapi_cache_vote_percent_average.value AS votingapi_cache_vote_percent_average_value FROM node node INNER JOIN users users ON node.uid = users.uid WHERE (node.status = '1') AND (node.type IN ('deal')) ORDER BY DESC LIMIT 0, 5 in /var/www/html/dealhaus/includes/database.mysqli.inc on line 156.

... when I activate Secure Pages with the following settings used:

Enabled
Switch back...
Make only secure pages listed: user/*, admin*

I was pulling my hair out to identify which module was primarily responsible for the error. I have no issues otherwise, SSL is set up correctly, and I even use this version on another server with no issues. This is on a fresh install. I'm guessing it's an issue with Secure Pages interacting badly with another module; disabling Secure Pages seems to fix the problem.

Any ideas?

Comments

gordon’s picture

gordon commented

This is not secure pages problem. Secure pages does nothing with the sql or nodes. It only looks at the existing path and redirects it needed.

Anonymous’s picture

Anonymous (not verified) commented

Thanks for the reply.

What I'm looking for here I suppose is if anyone has any experience with a similar issue.

Activating Secure Pages is certainly the catalyst...turning it on with the settings I listed does the trick every time. Like you say, it's probably not an issue directly with Secure Pages. But you don't know unless you ask.

Leaves me in a bit of a weird place though...I'm going to have to essentially rewrite the module so I can find the issue. I need some pages to be secure.

Hopefully someone else has seen this behavior.

grendzy’s picture

grendzy commented
Status: Active » Closed (won't fix)

The 5.x branch is no longer supported. If this issue is still present in a current version of Secure Pages, please update the issue summary, change the version field, and re-open the issue.