eeSiteKit | Support Forums | Kit_display/Single_entry

Kit_display/Single_entry - 404 problem / language related?

Mar 16, 2010 11:09am MartinH Total Posts: 12	EDIT: Ooops, I meant to post this in the 2.0 section ... I’m using eeSiteKit 2.2 on 1.6.8 latest build, running on my macbook for now. Hi, Just running through my first set up of eeSiteKit and hit upon a problem - whenever I had content in the extended_content field & click on the “Read more” link on the page, I was getting bounced to the 404 error page. After some debugging I traced it to the kit_display/single_entry template. The following code block was evaluating to true for some reason : `{!-- Checks entry title against segment_3 of the URI when template is displaying non-host-language content.--} {if embed:host_language != 'true' AND segment_3 != main_url_title_{embed:site_language}} -----redirect to the 404 page {/if}` I have not yet set up multi-language features (although I will - Kurt remind me to send you the French files once I’ve done so you can include in future releases if you like) yet. To debug I asked the template to output the values of host_language & site_language instead of redirecting, and I have host_language = ‘true’ and site_language = ‘english_usa’. entry_var is getting set to url_title so I guess the assign_variable at the top of the template is recognising host_language = ‘true’, from which I’d guess that the segment_3 != main_url_title_(sitelang) evaluation is giving an issue. My kit_language/english_usa template looks fine and the values seem to be getting passed in the embed values OK. Did I miss something in the set-up - was I supposed to create main_url_title_english_usa field somewhere ? For now I’ve just modified the template to skip that check as I’m just getting used to the eeSiteKit way of working on my local machine! Thanks in advance !! Martin

Mar 18, 2010 12:03pm Kurt Deutscher Total Posts: 321	Hi Martin, Sorry to leave you hanging for 2 days. I have 3 or possibly 4 sites launching in the next 2 weeks and my “in” box is filling up faster than my “out” box. The last few builds of EE had a bug fix that caused other bugs in previously working code for both EE and eeSiteKit. More specifically, the bug had to do with the way simple and advanced conditionals worked within weblog tags, and the ability to set identical custom category field names. These two changes in EE’s functionality have given eeSiteKit some issues. Fortunately, EE’s dev team reversed the “bug fix” that broke the way simple and advanced conditionals work within weblog tags, so those issues were resolved. Unfortunately, EE’s dev team introduced this new “bug fix” that now requires unique custom category field names. At this point I’m not sure if they will reverse this second functionality change, and if not, then I’m going to have to come up with a new way of having eeSiteKit handle multilingual category url segments. For now, that segment_3 check for non-host language url_entry_titles may just need to be commented out. I’ll look into it soon, but I was hoping I could sway the EE dev team to restore the custom category field name functionality before I do too much recoding. The current build of EE makes some of the multilingual features appear buggy in eeSiteKit do to the change EE’s dev team made. If EE’s dev team reverses that second functionality, we’re back in business, if not, then I’ve got to find another way of doing things. So I’ve been waiting to see what EE’s devs do with the next build release. That sort of explain what’s going on “behind the scenes” for you?

Mar 19, 2010 12:30am MartinH Total Posts: 12	Thanks Kurt. I’m just doing a single language site for now so not a big deal. I’ve just made French the main host language & commented out that check. Out of interest - what is the latest 1.6.8 build that works with eeSiteKit (looks like 20090915 was the release that “fixed” the duplicate custom category fields?) & are the problems carried forward into ee 2.0 ?

Apr 07, 2010 10:42am Kurt Deutscher Total Posts: 321	Hi Martin, Both the current builds of EE 1.6.8 and EE 2.0 Public Beta disallow the creation of duplicate custom category fields, so the multilingual functionality of eeSiteKit will not work correctly in those builds unless the fields are added by hand into the database. eeSiteKit works fine, but EE prevents you from creating the duplicate fields. However, if the duplicate fields are already there, or if they are added by hand to the database (something only advanced users should try), then the kit functions just fine. The thing is, the purpose of the kit is to work off of the strengths of EE, and we would never want to require users to create fields by hand in the database. We’re hoping to find a way around this in the near future.