Old theme to new product?

GlennBrogan · 2012-10-19 12:18:43

sent through your photography website contact page thank you!

GlennBrogan · 2012-10-22 15:28:06

Matt, is there a way to email you directly regarding this?

Matthew · 2012-10-22 17:05:44

Regarding what? ·?

Matthew · 2012-10-22 17:11:48

I took another look at your old pages. Instead of ·, try using •.

GlennBrogan · 2012-10-23 00:27:48

indeed I was requesting you email me regarding the • as that is also not working. The page so far with the new TTG CE2 CRG gallery is: http://www.glennbrogan.com/events/metric_hob_10_6_2012 and even on the login screen you can see the difference to the rest of my site. I am past the guessing and trying phase, and would love for you to just give me the solution. I should not have to be spending this much time on something that was in the original product that I bought and hence all over my coding. Let me again repeat that I am NOT a coder, but a photographer and would like to spend more time looking through the glass and not on my ass trying to figure this out. My exact phplugin string as it relates to the "nav-container" is as follows:

// SITE-WIDE "TRADITIONAL" NAVIGATION MENU
// This function establishes a site-wide navigation menu using pseudo-absolute URLs -- portable, domain agnostic, and without the location limitations of relative URLs
// Serves as an example of a function being applied globally
function ttg_header_navigation( $style, $path ) {
echo '
<div id="menu-container" class="menu-container traditional">
<div class="menu-content">

<p class="nav-container">
<a href="http://www.glennbrogan.com/index.html">Home</a> •
<a href="http://www.glennbrogan.com/gallery.html">Galleries</a> •
<a href="http://www.glennbrogan.com/about.html">About</a> •
<a href="http://www.glennbrogan.com/clients/">Clients</a> •
<a href="http://www.glennbrogan.com/blog.html">Blog</a> •
<a href="http://www.glennbrogan.com/links.html">Links</a> •
<a href="http://www.glennbrogan.com/contact.html">Contact</a>

</p>

</div>

</div>

';
return false; // Replaces normal menu
} // END

Matthew · 2012-10-23 02:03:22

It's working; it's just not styled. Replace • with:

<span style="color: #fff; margin-right: 25px;">&bull;</span>

That done, there is no guarantee that I will carry over every "feature" from previous versions. Some things are dropped for streamlining, because they create conflicts with new features, or because they just weren't very good inclusions to begin with. I intentionally drop things all the time, and have never made any promises whatsoever that features would remain from one version to the next if I feel they've outlived their welcome.

The intent of CE2 is not and has never been that it should be able to duplicate 100% designs from its predecessor(s).

GlennBrogan · 2012-10-23 02:13:02

Thank you very much Matt, it worked.

Matthew · 2012-10-23 02:16:27

With Halloween coming up, you might temporarily replace • with &dagger; =P

offline · 2012-10-25 04:39:18

I'm sympathetic to the issues here.

I've read (and printed out) all of the documentation regarding PHP that been posted, regardless of where it was posted.

And each time I think I've nailed it, I haven't. And I find myself starting at the beginning again.

Using the menus as an example was helpful, but more helpful that that would be a demonstration of how to implement the use of, the footer - for example, across the entire site. What changes would be made to the various files? which files? where would they go?

I know I want to define my headers and footers once. I'd like to pass the CSS from pages to be used site wide for font, color and etc.

Using PHP and CSS this should be easy, but I find it very complicated.

GlennBrogan · 2012-10-25 05:09:40

@Friedman, believe me, it is overwhelming. I just realized taht in the CE2 CRG engine, that If you change the data for the Auto Index, it changes the "meta: description" field in the Page setup section. janky at best. back before the ce2 and ce, they used to have details on each option and what it did and had videos clearly defining what each thing did. now they (TTG) have gotten so full of themselves and their coding that they talk down to all that ask for support or help and make you feel completely clueless and belittle you with their "superior knowledge" as they attempt to solve your issue while telling you to read documentation that is really just an overview anyway. I have read the forums here and the old CE forum ( http://forum.theturninggate.net/viewforum.php?f=7) , and the customer service standpoint is always the same "read sketchy overview and figure it out" or "here is the answer, but you should have read the janky overview doc file to somehow figured out your specific issue from it" or "I dont support previous versions because they are old (2 years)". I wil lbe writing a blog about my TTG experiences in the near future. Believe me, I love the product, but it is way too unstable as seen by all of the issues many users have, and also the customer support is fast but unfriendly. *note: Rod, not directed at you* just look at the last few messages I have gotten ( http://community.theturninggate.net/top … o-ce2-ai/) , blaming hosting for issues that are clearly not, but instead are coding Issues with files exported by the CE2 AI software. for proof read taht entire thread for his "solution" that worked (which involved me going into exported AutoIndex files and changing 3 lines of code generated by CE2 Auto Index that are NOT changeable in the Lightroom Engine.

Matthew · 2012-10-25 10:31:47

Code that would never have needed to be changed if your host had correctly configured its servers, which it has not.

And two years may not seem old to you, but that's a long time on the Internet. Especially when I'm working on this stuff every day to make it better and to keep it moving forward. It's just me and Ben here -- mostly me -- and so it's simply impossible for me to keep continue supporting obsolete versions of the plugins that I haven't even looked at in two years. Maybe if I had a crack team of digital engineers and an office full of support staff, but I don't. And if I did, the plugin prices would be way up to pay for it all.

And as for this thread and my annoyance at having to deal with it, the entire gist of the the thread is you continually attempting to jam a square peg into a round hole. I gave you good advice, and you stubbornly opted to ignore it and plunge onward with depreciated menus and bad hosting. You could have been finished in a few hours had you looked into a different hosting company, but instead chose to drag this out for days upon days while you wrestle with GoDaddy. That's your choice. But if you're going to ignore my support, then don't criticize me for not wanting to support you or having no other advice to give. The fact that I'm still here at all should tell you something, but here you're crapping on me for that too. Because apparently it's my fault that you want to make things 100x harder than they need to be.

GlennBrogan · 2012-10-25 20:40:03

Matt, let me start by saying I love the TTG product and I understand your position too, but honestly you need to come down a bit when people ask for help. If you read this thread, you gave me the wrong answer repeatedly for the first 9 messages. If thats not telling me to put a square peg into a round hole... matt, if people ask questions and pay for the product, don't be so quick to say "documentation" but just help them out. maybe copy/paste the actual lines from your documentation that pertains to them and then include a link so they get it, but also give them the answer. I was only asking questions to something I didnt understand and you were all about preaching documentation, I have read the documentation to both of the CE2 products I have purchased and use... they are very much summaries. I also read the PHPlugins documentation and the "All I ever needed to know about Auto Index", but in reality, I needed more information. I appreciate your speedy responses and appreciate Rod helping out, but if I ask a question, it is because I do not know the answer, it is not just something to do for me. At the end of the day Matt, I just want to shoot pix and upload galleries for clients. I upgraded because I found the CRG to be a better delivery to my clients. I will say again Matt, that I have been with you since before CE, back when all plugins were TTG. I will say 2 things about then:
1) the documentation was MUCH better explained in writing and even Video Clips - MUCH BETTER! I want to know what each line of change in the Lightroom engine will do so I may better use it.
2) after the purchase, I was not added to a mailing list or whatever, so I had no idea that there was a CE2-CRG to spend more money on, I stumbled upon it by accident.

Matt, I talk about your product to my friends and love it. I just want you to know that. My site is now fully up and running with the Old TTG pages shell, 10 new CE2-CRG Auto Index pages, PHPlugins, and a mixture of TTG highslide pro and CE2 CRG galleries, along with some assorted html pages I have added. I thank you for the products you offer and I wish you success in making better things. GoDaddy has been nothing but supporrtive in ALL of this and I thank them very much for their help as well. I love GoDaddy and have been with them for YEARS with no problems or issues.

one more question, just so I understand it, why is it that in the CE2 CRG engine If you change the data for the Auto Index, it changes the "meta: description" field in the Page setup section? shouldn't they be seperate?

Glenn B.

Matthew · 2012-10-25 21:48:32

They used to be separate, but someone suggested combining them -- I forget who or why -- and it made sense to do so. Both take a short description of page content, so it seems unnecessarily redundant to deal with them separately.

GlennBrogan · 2012-11-28 13:33:14

Although they "both take a short description of page content" one of those is what the Auto Index uses for text on the AutoIndex page, and therefore I do not think they should be the same. Otherwise there would not be two different names and locations within the engine for them. I can see where I would want to have different information in the 2 fields and only have one showing to the public at large looking at my AutoIndex page. I guess I will be content in calling that a minor glitch and you will be content in giving no real reasoning for the conjoining of those fields.

Matthew · 2012-11-28 13:38:32

It's not a glitch, because it's fully intentional. The conjoining of fields is just to have that information accessible from both areas where it is relevant.

If you're viewing a page in your auto index, you will see a Title and Description. If viewing that same page in Google search results, you will also see a Title and Description.

Those titles and descriptions should be the same, and I should not therefore require users to enter the same data twice.

GlennBrogan · 2012-11-28 13:40:42

thank you for your quick response

Community @ The Turning Gate

#26 2012-10-19 12:18:43

Re: Old theme to new product?

#27 2012-10-22 15:28:06

Re: Old theme to new product?

#28 2012-10-22 17:05:44

Re: Old theme to new product?

#29 2012-10-22 17:11:48

Re: Old theme to new product?

#30 2012-10-23 00:27:48

Re: Old theme to new product?

#31 2012-10-23 02:03:22

Re: Old theme to new product?

#32 2012-10-23 02:13:02

Re: Old theme to new product?

#33 2012-10-23 02:16:27

Re: Old theme to new product?

#34 2012-10-25 04:39:18

Re: Old theme to new product?

#35 2012-10-25 05:09:40

Re: Old theme to new product?

#36 2012-10-25 10:31:47

Re: Old theme to new product?

#37 2012-10-25 20:40:03

Re: Old theme to new product?

#38 2012-10-25 21:48:32

Re: Old theme to new product?

#39 2012-11-28 13:33:14

Re: Old theme to new product?

#40 2012-11-28 13:38:32

Re: Old theme to new product?

#41 2012-11-28 13:40:42

Re: Old theme to new product?

Board footer