There’s nothing more important than the customer

Well thanks, I’m liking how Solspace does business!

I’m still pretty well baffled by poor Olde Stone.

I can say one thing, Parsimmon Ridge is a problem because the url title of parsimmon-ridge exists twice in the DB. The Favories module wrongly assumes that url titles are unique across a site’s blogs when in fact url titles are unique only within a given blog. So favorites thinks it finds a successful match on one of the two parsimmon-ridge entries, saves it and starts the confusion.

As for olde-stone. ugh. No idea.

mk

Hey Mitchell,

Thanks for taking a look at the site, I appreciate it. Makes sense why the confusion is happening. As for Olde Stone, I simply went ahead and renamed the entry to “the club at olde stone” rather than “olde stone” and that seems to have fixed the favorites issue with it. I may have to do the same thing for Persimmon Ridge.

Were you able to see anything as for why the ratings were not showing up on Persimmon Ridge and Olde Stone (along with others possibly… I haven’t checked all of them).

I assumed it was because of this same thing, with there being two entries named the same, but after renaming Persimmon Ridge in one of the weblogs to something else, the rating still didn’t show up. Here is the entry where the review/rating isn’t showing: http://www.kentuckygolfing.com/courses/details/persimmon-ridge-golf-club/. The review is recorded because I can see it in the Modules >> Rating section and it also shows up on the main Courses page as being rated: http://www.kentuckygolfing.com/courses/ but the actual review doesn’t show in the single entry page.

Mitchell Kimbrough - 07 July 2008 06:31 AM

I’m still pretty well baffled by poor Olde Stone.

I can say one thing, Parsimmon Ridge is a problem because the url title of parsimmon-ridge exists twice in the DB. The Favories module wrongly assumes that url titles are unique across a site’s blogs when in fact url titles are unique only within a given blog. So favorites thinks it finds a successful match on one of the two parsimmon-ridge entries, saves it and starts the confusion.

As for olde-stone. ugh. No idea.

mk

Was thinking about this again today and have another question if you have a sec? I’m just wondering if there is a fix for this bug (if it’s even considered a bug?). I can only assume that this very same thing (having the same url_title in the database twice for different weblogs) is what’s causing some of my troubles for the reviews/ratings. This will continue to be a problem for me since with this golf site I have a course database with details on every course in the State… then I have a “course spotlight” section where I write reviews on individual courses after I play them. So, the course name will already be in the database for the course details and then it will end up in the database for a second time when I write an article in the “course spotlight” section.

So… if there is a fix so I can specify one weblog to use for the module instead of it looking at the weblogs sitewide that would be great. If not, do you suggest that I just be conscious of this in the future and simply add a “1” or other verbiage to the end of the url_title when I write an article in the “course spotlight” section so that the url_title only shows up once in the database? Would that be the easiest approach around this issue?

deronsizemore - 17 July 2008 06:19 PM

So… if there is a fix so I can specify one weblog to use for the module instead of it looking at the weblogs sitewide that would be great. If not, do you suggest that I just be conscious of this in the future and simply add a “1” or other verbiage to the end of the url_title when I write an article in the “course spotlight” section so that the url_title only shows up once in the database? Would that be the easiest approach around this issue?

That’s strange…. shouldn’t EE automatically be adding “1”, “2”, “3’ etc to duplicate name entries?
EDIT

Pie Man - 18 July 2008 07:31 AM

deronsizemore - 17 July 2008 06:19 PM

So… if there is a fix so I can specify one weblog to use for the module instead of it looking at the weblogs sitewide that would be great. If not, do you suggest that I just be conscious of this in the future and simply add a “1” or other verbiage to the end of the url_title when I write an article in the “course spotlight” section so that the url_title only shows up once in the database? Would that be the easiest approach around this issue?

That’s strange…. shouldn’t EE automatically be adding “1”, “2”, “3’ etc to duplicate name entries?
It’s impossible to have two entries with the same url_title…. except with MSM

Ehhh… not sure to be honest. Maybe EE automatically adds a 1, 2, 3, etc., to duplicate entries within the same weblog? I’ve never had a setup like this before with previous sites so this is all new territory for me.

Since I’m dealing with two different weblogs that have the same entry titles, thus having the url_title automatically generated from that, maybe it allowed duplicates? I’ll see if I can find an answer on the EE forums and if I can’t, post there asking.

For now, instead of manually adding a “1” or whatever to the end, I just went into the “course spotlight” weblog and added a simple prefix to be appended to the beginning of the url_title for all new entries. Simple fix for this problem but still might be a bug on EE’s end if it’s suppose to be adding 1, 2, 3, etc., to duplicate entries.

Deron,

Can I take a peek in your CP?

Pie Man - 18 July 2008 08:36 AM

Deron,

Can I take a peek in your CP?

Definitely. PM sent.

EDIT

Weird… I wasn’t sure what the default behavior should have been.

Here are the extensions I have enabled:

- User authors
- User
- Accessible Captcha
- Cool Location
- Favorites
- Parse Rating Stats
- Multi Relationship
- Edit Tab Ajax

I think I’ll pop in at the EE forums and ask about this weblog behavior too.

deronsizemore - 21 July 2008 09:10 AM

I think I’ll pop in at the EE forums and ask about this weblog behavior too.

Good idea

Unless there’s a setting I’m unaware of… 

Here’s the thread and response for what we’ve been discussing: http://expressionengine.com/forums/viewthread/85820/

I guess that makes me an idiot haha
Looking back, I also realized my testing was flawed… long story, hehe

So I’ll note this as a bug…. and thank you for your patience

Pie Man - 21 July 2008 01:15 PM

I guess that makes me an idiot haha
Looking back, I also realized my testing was flawed… long story, hehe

So I’ll note this as a bug…. and thank you for your patience

No problem. Thanks for checking into it for me.

BTW: Is there generally a time frame for when bugs are fixed? Or is it just whenever the next version release comes out?