Jeff Adams

Hope this helps, I’m super tired, goodnight! 🙂

I just familiarized myself with the documentation better. I was coming to it from google searches or links via the forum. This made it seem like the documentation was all over the place. But it actually is organized very well. It could be more elaborate or detailed at least and maybe have videos throughout but I imagine it may evolve over time.

MY LESSON LEARNED
I had forgotten about the “help” drop down under the GD Dashboard. But, even still, that initial page is rather intimidating at first. But if anyone in the future is reading this I could have potentially found this by clicking on that Help drop down at the top right corner of the GD dash and then clicking the link inside of the sentence “Should you need help understanding, using, or extending GeoDirectory, please read our documentation”. There is a search field at the top of that says “search GeoDirectory V2 Documentation” and putting in “Link Posts” as it appears could have got me to the CPT’s documentation. 🙂 I’ll have to try that more often!

Oh, so only admins will see this, can admins set and/or change the date or is it something that the package sets?

Thanks, a man can only dreams sometimes, lol. I’ll just have to struggle with trying to discern the best way to move forward. I suppose keeping as much under one CPT as possible is in order. This may force me into keeping things simple I suppose. At least I’m trying to stay positive because this part of creating a directory with GD has always been the hardest to overcome and I’ve never really been happy with my end decision.

Like VeganLinked.com I feel has been built with too many CPT’s. It’s mostly a problem with joining and end users using the site, which are the two most important things. I think the next directory I build (to test V2 in and hopefully turn into something viable to run with) will start off with the default places and events…

Thanks again for your time Alex!

Ok, so I don’t really see “Link Posts: Event” but I see where it discusses linking CPT’s. I guess i’m seeing Link Posts: Event because that’s a default CPT and displaying in the “predefined fields”. I’m assuming that if I create more CPT’s they will also appear in the Predefined fields?

I remember now actually going to the document you referred to earlier today before I posted this, not sure it was for this though. It doesn’t mention the predefined fields or the words “Link Posts” so I must have looked right past it. This idea of Linking Posts, I guess initially I was thinking it would be found somewhere else, not under CPT. But, now it makes sense. It’s new, maybe the word “New” would help older users like me zone in on things like this because I’m not sure much else is different about CPT’s… 🙂 And, I may have overlooked this too, but if I’m correct, it would be great if the documentation explained that new CPT’s will be added to the predefined fields.

This reminds me of when verbiage changes between things how confusing it can get. Either the documentation ideally would say “Link Posts:” or the predefined field would say “Linked CPT”. Kind of like plugins ideally would be named the same way as they appear in the download area of the site (something I’m reminded of every time I have to deal with the plugins). Sometimes the little things that help a lot 🙂

This Linked Posts seems like a super awesome feature!!! I look forward to the possibilities with it. I can see using this in some powerful ways! Thanks for your patience!

Yeah, I tried creating another Map API and I noticed a statement somewhere saying it may take 5 minutes for the changes to take effect so I think recreating my Map API fixed the problem and waiting… 🙂