This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
March 18, 2011 12:01pm
Subscribe [5]#16 / Mar 31, 2011 11:41pm
Lori,
I also would suggest trying some extra parameters in your weblog:entries tags just to rule out a status or future date issue.
{exp:weblog:entries weblog="assignments" limit="1" disable="trackbacks|pagination|categories" entry_id ="{segment_3}" status="not closed" show_future_entries="yes"}
<h3>{title}</h3>
<p>Segment 4: {segment_4}</p>
<p>{/exp:weblog:entries}Let us know how you make out.
#17 / Apr 01, 2011 10:17am
Hi Lisa & John,
Lisa:
- When I add the dynamic=“off”, it shows newer posts for the members 10-99, but please see my posts above. I never needed to use the dynamic=“off” before and don’t need it for members 1-9 & 100+.
John:
- When I added your code, nothing changed from my stated problem.
——
In my html_header I’m using another weblog entries loop which processes the title of the entry. I have removed that during tests so that isn’t affecting the problem although the same problem occurs as you’ll see in my screenshots below.
——
Scenario 1 - Problem occurs when:
- Entry is newer than 10/5/2010 (client created posts on this date, then opens each one up on future dates as needed)
AND
- Member_id in URL is between 10-99.
Scenario 2 - Content correct shows when:
- Member_id in URL is between 1-9 & 100+
Scenario 3 - Content correct shows when:
- Entry was originally created on 10/5/2010 (client created posts on this date, then opens each one up on future dates as needed)
- Member_id in URL doesn’t matter if the content is older
Scenario 4 - Content correct shows when:
- Add dynamic=“off” to weblog entries loop.
OR
- Remove member_id from URL
* Please see other posts why I don’t think this is the solution.
Please see my screenshots (I labeled them with the scenario) to help you visualize what’s happening.
Thanks.
Lori
#18 / Apr 01, 2011 10:59am
Hey, L2,
We really need this tested in the bare minimum template. That means none of your display; only the weblog entries tags we’re having you try. There should be nothing else at all in the template ,and the output would be black test on a white page.
Can you give that a shot? There can be a lot of other things happening in the template that would impact this display, so we need to really isolate it.
Thank you.
#19 / Apr 01, 2011 11:06am
Hi Lisa,
I removed all other code from my template and placed in the code you suggested. Same problem. I see it for member_id 1-9 & 100+, but no members in between.
Here’s my page code:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html >
<!--HEAD SECTION-->
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
<title>test</title>
</head><!--End Head-->
<!--BODY SECTION-->
<body>
{exp:weblog:entries weblog="assignments" limit="1" disable="trackbacks|pagination|categories" entry_id="{segment_3}" status="not closed" show_future_entries="yes"}
<h3>{title}</h3>
<p>Segment 4: {segment_4}</p>
<p>{/exp:weblog:entries} </p>
<p></body><br />
</html>Thanks!
Lori
#20 / Apr 01, 2011 11:30am
Going out on a limb here, but could there possibly be an issue with having a 2-digit member_id? Seems like if it’s 1-digit or 3-digits it works fine.
I just typed in a 3-digit number (980) in the URL where the member_id would go and the page showed. This isn’t even a valid member_id.
Using phpAdmin could I change someone with a 2-digit member_id to be a single digit to test it? If so, do you know where all of the member_ids are stored?
Thanks.
Lori
#21 / Apr 01, 2011 12:14pm
I think I may have figured it out although I’m not sure why this matters. There must be some type of conflict between having the entry_id in segment_3 and member_id in segment_4.
If I change the entry_id to be the url_title in the URL string then the page shows regardless of member_id and when the entry creation date.
Perhaps having a 4-digit segment_3 and a 2-digit segment_4 is a problem?
Does this make sense to you guys?
I’d prefer to have the entry_id in the URL instead of the url_title, but if that’s the only way I can get it to work moving forward then that’s what I’ll do.
Thanks!
Lori
#22 / Apr 01, 2011 1:57pm
Hi, Lori. Having the entry_id and a member_id in the same url may be the issue, and if swapping out segment_3 to use the url_title works, then stay with it. We don’t normally see people appending member_ids in a url.
So will that work for you?
#23 / Apr 07, 2011 7:11pm
Hi Sue,
My concern is that it was never a problem before - it just started happening suddenly so maybe something else is the cause.
I’ve read another post concerning the DST issue where it is adding an hour to the time. All of the posts that aren’t an issue were previously created and “closed”, then the admin would open one at a time over the course of 5 months. It’s the new items that he’s creating now that are causing a problem in this weblog. Could it possibly be a time issue or maybe 2011 vs 2010? I’ve tried to manually change the time directly in the database and it didn’t seem to make a difference but perhaps I didn’t change the right thing. I was hoping to change it to a date that was working. Any idea on how I could do that?
Thanks!
Lori
#24 / Apr 08, 2011 7:48am
The only real way to change the date/time is within the edit entry section of the control panel itself. The entry date isn’t human readable, it’s format isn’t something you could look at and say.. let’s change it by fiddling with what’s there.
EE 1.7.1 was released yesterday (see the change log.
Could we have you back up your database and upgrade? It may not be the answer to this particular problem, but it’s the next step to take.
#25 / Apr 18, 2011 3:43pm
Hi Sue,
I updated to EE 1.7.1 this morning and I still have the problem.
However, now…
- if I have a member_id after the entry_id in the URL no post will show. I have to first remove the member_id from the page.
- I even tried adding “hi” instead of the member_id and that broke it too.
Previously…
- any number between 1-9 would work, and 100+ for all posts
- if post was dated in 2010 but opened afterwards it work work for all member_ids
- if post was dated in 2011 and member_id was between 1-9 would work, and 100+
What works:
- If I remove the 4th segment entirely
- if I use the url_title instead of the post entry_id
Observations:
- Perhaps something has changed in the update from 1.6.9 to 1.7.1 because I’m getting different results.
- Is there something about having a number in the 3rd segment and something else (number, text) in the 4th?
- Since the upgrade to 1.7.1 I am now experiencing the problem in all of my sections not just one as previously stated.
- If I use a barebones template and try to pull the member_id, it will show me the member_id of the author of the post, rather than the logged_in_member_id.
Thank you!
Lori
#26 / Apr 19, 2011 11:37am
I figured out a solution to the issue. I’m not sure if my issue was due to a bug in EE or not, but regardless I was able to rewrite the code to solve the problem.
Because there seemed to be a problem with having the entry_id in the URL along with some text in a following segment, I needed to put dynamic=“off” and entry_id=”{segment_x}” in the weblog entries tag.
I appreciate all of the tech support to try to help with this problem. You can close this thread.
Thanks.
Lori
#27 / Apr 19, 2011 1:04pm
Hey Lori,
Glad you got this working. I don’t think it’s a bug in EE, but rather the way URLs work. EE makes a “best effort” to determine what content to show, and it just wasn’t what you wanted in this case.
Thanks for sharing your solution as well!