Developer
Supported
Sitemap Module
ExpressionEngine 2, ExpressionEngine 3, ExpressionEngine 4, ExpressionEngine 5, ExpressionEngine 6
Back to this add-on's main page
View Other Add-ons From PutYourLightsOn
Future entries code commented out
Support Request
Dylan Smith/Contextdesign
|
Posted: 26 February 2011 09:43 PM |
|
|
|
The code that seems to eliminate future entries from appearing in a sitemap is commented out:
~ line 134 in mod.sitemap.php:
// if future entry date then don't include if ($entry['entry_date'] && $entry['entry_date'] > time()) { continue; }
|
|
|
PutYourLightsOn
|
Posted: 27 February 2011 03:27 PM |
# 1
|
|
Developer
|
dylan, which version of sitemap are you on? i don’t see the line commented out in version 2.1.3
|
|
|
Dylan Smith/Contextdesign
|
Posted: 27 February 2011 09:59 PM |
# 2
|
|
|
Check the 1.x version. I pulled a new d/l of it yesterday, just to see if it was fixed.
I’ve been running 2.0.1, which I opened up yesterday to do some more hacking on, and noticed the line was commented out. It’s still commented out in 2.1.3.
|
|
|
PutYourLightsOn
|
Posted: 27 February 2011 10:34 PM |
# 3
|
|
Developer
|
what text editor are you using to view the file? in 2.1.3 version for 1.x i see:
// if future entry date then don't include if ($entry['entry_date'] && $entry['entry_date'] > time()) { continue; }
|
|
|
Dylan Smith/Contextdesign
|
Posted: 28 February 2011 12:21 AM |
# 4
|
|
|
BBEdit.
It looks like there are a bunch of spaces after the comment, before the if statement. Putting a return in there instead fixes it easily enough. The “format date for location” line had the same thing going on.
Also, I just found a bunch of gremlin characters by using BBEdit’s Zap Gremlins tool.
|
|
|
PutYourLightsOn
|
Posted: 28 February 2011 08:19 AM |
# 5
|
|
Developer
|
ok i’ll clean up the spaces, thanks for reporting this!
|
|
|
Dylan Smith/Contextdesign
|
Posted: 28 February 2011 11:49 AM |
# 6
|
|
|
You’re welcome; no problem.
On a different topic, have you had a chance to address the server offset issue? That’s why I went in to poke around, but I imagine you’d have a better solution than what I came up with.
cheers,
d.
|
|
|