New Response

« Return to the blog entry

You are replying to:

  1. So I can understand and make it concrete using your web site. Each page in the DB has a "page URL name".

    The sections are each a separate page:

    - Accounting software

    - Support

    - Integration

    - References

    - News

    - About Us

    Under Accounting software there are some categories, which are also separate pages such as:

    - Functionality Overview

    - Security and Operations

    Beyond this there are what you call "page URL name". One entry under Security and Operations is:

    - e-conomic technical setup

    So does this mean that there has to be a separate rule for each section plus one for each category? Let me see if I can write a couple of substitution rules based on your patterns.

    For the section "Accounting software" the actual URL is:


    The substitution rule that applies is (I think):

    /[section name]/* -> /[db path]/[db name]/[view name]/w-[page URL name]-*

    Doing the substitution manually using "x" for the db path, "y.nsf" for the db name, "z" for the view name and "accountingsoftware" for the page URL name, we get:


    Is that right?

    For http://www.e-conomic.com/accountingsoftware/security/ we would use this pattern:

    /[section name]/*/* -> /[db path]/[db name]/[view name]/w-[page URL name]-*-* and get


    And finally for:

    http://www.e-conomic.com/accountingsoftware/security/technical-setup we would use the same pattern and get


    I think I've got it. Quite a nice solution except for having to create so many substitution rules. In my scheme I only had one level so I only needed one rule.

    Thanks ever so much. I'm going to have another go at this.



Your Comments