[ZCM] [ZC] 2244/ 2 Reject "Zope 2.10/ZPT - TALError: Path element may not be empty .."

"Collector: Zope Bugs, Features, and Patches ..." <[email protected]>
Newsgroups gmane.comp.web.zope.devel.collector-monitor
Message-ID <[email protected]>
Issue #2244 Update (Reject) "Zope 2.10/ZPT - TALError: Path element may not be empty .."
 Status Rejected, Zope/bug medium
To followup, visit:
  http://www.zope.org/Collectors/Zope/2244

==============================================================
= Reject - Entry #2 by ajung on Nov 23, 2006 4:05 am

 Status: Accepted => Rejected

Stupid user error.. the path expression contains a double slash :-/
________________________________________
= Request - Entry #1 by ajung on Nov 22, 2006 2:51 pm

 Status: Pending => Accepted

 Supporters added: philikon

While making TextIndexNG3 compatible with Zope 2.10 I encountered the following bug with a view registered through Five: 

 ['Compilation failed', "zope.tal.taldefs.TALError: Path element may not be empty in 'context//@@words_vocabulary' in expression 'nocall: context//@@words_vocabulary', at line 33, column 3"]

The related ZPT code looks like this:

<tal:if condition="request/pattern|nothing" >
  <div tal:define="wv nocall: context//@@words_vocabulary;
                   words python: wv(request.get('pattern'), request.get('language'))">
    <ul>
      <li tal:repeat="word words">
        <a tal:attributes="href string:documentsforword?word=$word" tal:content="word" />
      </li>
    </ul>
    <span tal:condition="not: words">No matching words found</span>
  </div>
</tal:if>


==============================================================
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.