Site Index Portlet and Folder names with quotes

Hi,
I don't know if anyone else has hit this problem with the site index portlet, but it fails to render when the page group contains a page with a quote >'< in the page name.
This is an issue particularly using O Drive and 10.1.4 portal, as the page name and page display name both get set to the folder name & windows alows quotes in folder names.
The portlet code escapes the display name, but not the page URL. In 10.1.4 the URL has the page name in it, including any quotes, so the URL needs to be escaped too.
This is achieved by modifying the code in site_index_tree.process_tree. Have a look how l_title_enc is set & do the same for the l_link value. l_link_enc := replace(l_link, '''', '\''');
Comments and suggestions welcome.
Cheers,
David

Hi
to avoid this problem I'm afraid that you have to avoid quotes from your pages names.
Quotes in URL are not supported by navigators so you can't use them for pages names (but,as you said you can use for display names).
A possible workaround is to modify the render_tree method, replacing URL by permanent links.
Your url http://myportal/page/portal/page/apage/anotherpage/namewithquote will be replaced by something like :
http://myportal/page/portal/page/54564F654SD5F4SD56F4SD564FS
Hope this will help

Similar Messages

  • Smart collection and folder names with "_"

    I have problems when making Smart Collections based on folder names
    My folder name is 2009_11_20 Mist
    When I make a Smart collection with "Folder" Stars with 2009
    I get a lot of files
    When I change the  2009 to 2009_11 I get no files. Even when I make 2009_ I get no files
    When I change the 2009 to Mist and the "Starts with" to "Contains" again I get the desired files.
    When I change the 2009 to 2009_11 and the "Starts with" to "Contains" again I get no files.
    It seems that LR with Smart Collections cannot handle the "_" character???
    Who can help?

    It's a bug. The usual workaround is to use hyphen as the separator in your folder names instead of an underscore.

  • Site Index Portlet problem !

    Hello everyone.
    I have installed the Site Index Portlet and corrected the line-feed problem with the text. My problem is that I have a portal with 2 languages (English default, Greek) and the Site Index Portlet cannot understand the change of the language (using the built-in language portlet). Do I have to run the ptlnlsi.sql script twice (one for English and one for Greek messages) ? And how is this possible since the ID and DOMAIN columns are primary key (get unique constraint error) ?
    Finally, is it possible that this portlet support 2 languages at the same time ? Although I deleted all messages that ptlnlsi.sql inserts and run it again only with el (that's for Greek) parameter still the portlet works only at the English instance of a page and not the translated. Is there a solution ?
    Thanks in advance.

    Hi
    to avoid this problem I'm afraid that you have to avoid quotes from your pages names.
    Quotes in URL are not supported by navigators so you can't use them for pages names (but,as you said you can use for display names).
    A possible workaround is to modify the render_tree method, replacing URL by permanent links.
    Your url http://myportal/page/portal/page/apage/anotherpage/namewithquote will be replaced by something like :
    http://myportal/page/portal/page/54564F654SD5F4SD56F4SD564FS
    Hope this will help

  • Site Index Portlet - Doesn't show page tree

    After installing the Site Index Portlet and adding it to the repository, portlet was visible and could be added to the page. However, it won't show the page tree of the sub-pages.
    Are there any configuration or options to look at to make the sub-pages/page tree visible?
    Portal version is 10g
    Thank you in advance,
    Jouni

    I run again with user Portal
    got the message successfully inserted all the strings
    but i am not sure it whent right as shows following queries
    select ID,count(*) from WWNLS_STRINGS$
    WHERE ID BETWEEN 45075 AND 45098
    group BY ID
    order BY ID;
    one line only exists per ID
    and then
    select SUBSCRIBER_ID, ID, DOMAIN, NAME, LANGUAGE,
    TEXT,
    substr(TEXT_START,1,30),
    BASE_STRING_ID, substr(TEXT_STRING,1,50)
    from WWNLS_STRINGS$
    WHERE LANGUAGE in ('us', 'fr')
    AND ID BETWEEN 45075 AND 45098
    order by LANGUAGE;
    field TEXT seems incomplete and having still NLs in it.
    I run it for Language us and Language fr but got only first version back
    Should I delete those entries first before reinserting them?
    Isnt there an easier way?
    I

  • Site Index Portlet - Permissions

    I am using the Site Index Portlet but having trouble with the permissions. We would like to use it as a Site Map on our web site, where there is no authentication for users. Does anyone know how to make this portlet available for public users to view? (I have tried adding the PUBLIC user to the provider, but no joy!)
    Any help would be appreciated!
    Thanks, Angela

    Yes, we are also having the same problem. I've also noticed that non-public pages will show up in the tree ONLY if you are the owner/creator of the page. It doesn't seem to look at any other group/user permissions.

  • Problems installing Site Index Portlet

    Hi,
    I get several errors trying to install the newest Site Index Portlet with the included batch file ptlsipi.sql within SQLPlus into Orcale portal for Appserver 10g (see errors below). PDK is properly installed.
    Any help would be fine...
    regards Bernd Hülsebusch
    SQL*Plus: Release 9.2.0.1.0 - Production on Mi Jun 1 14:45:51 2005
    Copyright (c) 1982, 2002, Oracle Corporation. All rights reserved.
    Verbunden mit:
    Oracle Database 10g Enterprise Edition Release 10.1.0.3.1 - Production
    With the Partitioning, OLAP and Data Mining options
    SQL>
    SP2-0423: Unzulässiger GET-Befehl
    SQL> @ptlsipi
    Installation of Site Index Provider
    Sequenz wurde gelöscht.
    Sequenz wurde angelegt.
    Creating Site Index NLS Package
    Warnung: Paket wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE SIP_NLS_INSTALL:
    LINE/COL ERROR
    7/1 PL/SQL: Declaration ignored
    7/37 PLS-00201: Bezeichner 'WWNLS_STRINGS$.NAME' muss deklariert
    werden
    12/1 PL/SQL: Declaration ignored
    13/30 PLS-00201: Bezeichner 'WWNLS_STRINGS$.LANGUAGE' muss deklariert
    werden
    Creating Site Index NLS Package Body
    Warnung: Paketrumpf wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE BODY SIP_NLS_INSTALL:
    LINE/COL ERROR
    0/0 PL/SQL: Compilation unit analysis terminated
    1/14 PLS-00905: Objekt BHUELSEB.SIP_NLS_INSTALL ist ungültig
    1/14 PLS-00304: Rumpf von 'SIP_NLS_INSTALL' nicht ohne die
    Spezifikation kompilierbar
    Benutzerzugriff (Grant) wurde erteilt.
    Installing the NLS Strings (English)
    l_language wwnls_strings$.language%type;
    FEHLER in Zeile 3:
    ORA-06550: Zeile 3, Spalte 26:
    PLS-00201: Bezeichner 'WWNLS_STRINGS$.LANGUAGE' muss deklariert werden
    ORA-06550: Zeile 3, Spalte 26:
    PL/SQL: Item ignored
    ORA-06550: Zeile 4, Spalte 26:
    PLS-00905: Objekt BHUELSEB.SIP_NLS_INSTALL ist ungültig
    ORA-06550: Zeile 4, Spalte 26:
    PL/SQL: Item ignored
    ORA-06550: Zeile 14, Spalte 4:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 14, Spalte 4:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 25, Spalte 4:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 25, Spalte 4:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 26, Spalte 4:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 26, Spalte 4:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 27, Spalte 4:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 27, Spalte 4:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 28, Spalte 4:
    PLS-00320: Die
    Fehler bei PACKAGE BODY SIP_NLS_INSTALL:
    LINE/COL ERROR
    0/0 PL/SQL: Compilation unit analysis terminated
    1/14 PLS-00905: Objekt BHUELSEB.SIP_NLS_INSTALL ist ungültig
    1/14 PLS-00304: Rumpf von 'SIP_NLS_INSTALL' nicht ohne die
    Spezifikation kompilierbar
    Creating Site Index Provider Package
    Warnung: Paket wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE SITE_INDEX_PROVIDER:
    LINE/COL ERROR
    67/5 PL/SQL: Declaration ignored
    69/32 PLS-00201: Bezeichner 'WWPRO_API_PROVIDER.COOKIE_TABLE' muss
    deklariert werden
    89/5 PL/SQL: Declaration ignored
    94/12 PLS-00201: Bezeichner 'WWPRO_API_PROVIDER.PORTLET_RECORD' muss
    deklariert werden
    135/5 PL/SQL: Declaration ignored
    143/12 PLS-00201: Bezeichner 'WWPRO_API_PROVIDER.PORTLET_TABLE' muss
    deklariert werden
    LINE/COL ERROR
    171/5 PL/SQL: Declaration ignored
    172/31 PLS-00201: Bezeichner
    'WWPRO_API_PROVIDER.PORTLET_INSTANCE_RECORD' muss deklariert
    werden
    189/5 PL/SQL: Declaration ignored
    190/31 PLS-00201: Bezeichner
    'WWPRO_API_PROVIDER.PORTLET_INSTANCE_RECORD' muss deklariert
    werden
    LINE/COL ERROR
    206/5 PL/SQL: Declaration ignored
    207/31 PLS-00201: Bezeichner
    'WWPRO_API_PROVIDER.PORTLET_INSTANCE_RECORD' muss deklariert
    werden
    242/5 PL/SQL: Declaration ignored
    243/33 PLS-00201: Bezeichner 'WWPRO_API_PROVIDER.PORTLET_RUNTIME_RECORD'
    muss deklariert werden
    Creating Site Index Portlet Package
    Warnung: Paket wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE SITE_INDEX_PORTLET:
    LINE/COL ERROR
    53/5 PL/SQL: Declaration ignored
    54/28 PLS-00201: Bezeichner 'WWNLS_STRINGS$.NAME' muss deklariert
    werden
    90/5 PL/SQL: Declaration ignored
    92/29 PLS-00201: Bezeichner 'WWNLS_STRINGS$.LANGUAGE' muss deklariert
    werden
    141/5 PL/SQL: Declaration ignored
    142/31 PLS-00201: Bezeichner
    'WWPRO_API_PROVIDER.PORTLET_INSTANCE_RECORD' muss deklariert
    LINE/COL ERROR
    werden
    158/5 PL/SQL: Declaration ignored
    159/31 PLS-00201: Bezeichner
    'WWPRO_API_PROVIDER.PORTLET_INSTANCE_RECORD' muss deklariert
    werden
    195/5 PL/SQL: Declaration ignored
    196/33 PLS-00201: Bezeichner 'WWPRO_API_PROVIDER.PORTLET_RUNTIME_RECORD'
    muss deklariert werden
    Creating Site Index Provider Package Body
    Warnung: Paketrumpf wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE BODY SITE_INDEX_PROVIDER:
    LINE/COL ERROR
    0/0 PL/SQL: Compilation unit analysis terminated
    1/14 PLS-00905: Objekt BHUELSEB.SITE_INDEX_PROVIDER ist ungültig
    1/14 PLS-00304: Rumpf von 'SITE_INDEX_PROVIDER' nicht ohne die
    Spezifikation kompilierbar
    Creating Site Index Portlet Package Body
    Warnung: Paketrumpf wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE BODY SITE_INDEX_PORTLET:
    LINE/COL ERROR
    0/0 PL/SQL: Compilation unit analysis terminated
    1/14 PLS-00905: Objekt BHUELSEB.SITE_INDEX_PORTLET ist ungültig
    1/14 PLS-00304: Rumpf von 'SITE_INDEX_PORTLET' nicht ohne die
    Spezifikation kompilierbar
    Creating Site Index Tree components
    Warnung: Paket wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE SITE_INDEX_TREE:
    LINE/COL ERROR
    12/3 PL/SQL: Declaration ignored
    12/32 PLS-00201: Bezeichner 'WWV_USER_CORNERS.TITLE' muss deklariert
    werden
    14/3 PL/SQL: Declaration ignored
    14/33 PLS-00201: Bezeichner 'WWV_USER_CORNERS.SITEID' muss deklariert
    werden
    16/3 PL/SQL: Declaration ignored
    19/18 PLS-00201: Bezeichner 'WWV_USER_CORNERS.ID' muss deklariert
    werden
    LINE/COL ERROR
    37/3 PL/SQL: Declaration ignored
    38/21 PLS-00201: Bezeichner 'WWV_USER_CORNERS.SITEID' muss deklariert
    werden
    Warnung: Paketrumpf wurde mit Kompilierungsfehlern erstellt.
    Fehler bei PACKAGE BODY SITE_INDEX_TREE:
    LINE/COL ERROR
    0/0 PL/SQL: Compilation unit analysis terminated
    1/14 PLS-00905: Objekt BHUELSEB.SITE_INDEX_TREE ist ungültig
    1/14 PLS-00304: Rumpf von 'SITE_INDEX_TREE' nicht ohne die
    Spezifikation kompilierbar
    Benutzerzugriff (Grant) wurde erteilt.
    Benutzerzugriff (Grant) wurde erteilt.
    Registering the Site Index Provider
    Geben Sie einen Wert für portal_schema ein: jak_portal
    l_prov_rec wwpro_api_provider_registry.provider_record;
    FEHLER in Zeile 2:
    ORA-06550: Zeile 2, Spalte 20:
    PLS-00201: Bezeichner 'WWPRO_API_PROVIDER_REGISTRY.PROVIDER_RECORD' muss
    deklariert werden
    ORA-06550: Zeile 2, Spalte 20:
    PL/SQL: Item ignored
    ORA-06550: Zeile 3, Spalte 20:
    PLS-00201: Bezeichner 'WWPRO_API_PROVIDER_REGISTRY.NODE_PROVIDER_RECORD' muss
    deklariert werden
    ORA-06550: Zeile 3, Spalte 20:
    PL/SQL: Item ignored
    ORA-06550: Zeile 7, Spalte 5:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 7, Spalte 5:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 8, Spalte 5:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 8, Spalte 5:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 9, Spalte 5:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 9, Spalte 5:
    PL/SQL: Statement ignored
    ORA-06550: Zeile 10, Spalte 5:
    PLS-00320: Die Typ-Deklaration dieses Ausdruckes ist unvollständig oder
    fehlerhaft
    ORA-06550: Zeile 10, Spalte 5:
    PL/SQL: Statement

    I had the same errors when running the install scripts under a user other than the portal administrator (PORTAL). Check that you run them with the correct user.
    Greetings,
    Frank

  • Site index portlet

    hello,
    I download site index portlet from oracle
    http://www.oracle.com/technology/products/ias/portal/point/siteindex/installation.html
    i follow the instructions succesgull
    but when in "Edit Defaults Mode" settings
    in page group selector list
    my page group does not appear!
    I can see only the defaults page groups ( portal desgin pages e.t.c)
    How      can I solve this problem?
    thanks,

    A few other options:
    - Do you use a language that can be used in the pagegroup? if not the select statement he uses will not find any data => try to switch to a language that was published for this pagegroup.
    - Just to make sure, can you make a select statement to the wwv_user_corners tabel from the schema in which you have installed the portlet?
    - dig into the html source code where you have put your menu on and try to get the url of the tree and open it(search render_tree_items), check if any values have been created for the menu.
    If this is empty you should try this select statement and try to find out what causes it not to give back any values:
    select level, siteid, id, title, parentid from wwv_user_corners t1
    where t1.siteid = '||p_siteid||'
    and t1.is_template != '||wwpob_api_page.PAGE_TEMPLATE_YES||' -- 0
    and t1.type not in
    ('||wwpob_api_page.PAGETYPE_TAB||' ,
    '||wwpob_api_page.PAGETYPE_MOBILE||' ,
    '||wwpob_api_page.PAGETYPE_NAV||' ,
    '||wwpob_api_page.PAGETYPE_CAT_PERS||'
    and t1.language = '''||p_lang||'''
    start with id = 1 and siteid = '||p_siteid||' and language = '''||p_lang||'''
    connect by prior id = parentid and siteid = '||p_siteid||' and language = '''||p_lang||'''
    order siblings by title;

  • Site Index Portlet is not refreshed correctly

    I have deployed the Site Index Portlet in Portal 10.1.4, and it seems to work nicely. However, sometimes the portlet does not refresh correctly, even though other elements on the page (e.g. banner, page path) are updated. Refreshing the page with F5 in Internet Explorer 6.0 (or clicking the same link once more) refreshes the content of the portlet, but this is unacceptable for end users.
    The same problem is not possible to reproduce in Firefox 1.5. If only all end users were using Firefox . . .
    Any ideas for how to fix this for all browsers?
    -- [email protected] [Senior Principal Consultant]
    -- http://home.c2i.net/toreingolf/contact/

    My browser caching is already set to "Every visit to the page", I'm afraid.
    I was suspecting the PPE in Portal, but if that was the reason, then the problem would occur in all browsers, right? Or do you think this could be caused by how IE handles ESI?
    Interestingly, the portlet works perfectly in Firefox (the menu is even updated immediately, before the new page loads!). And in Opera, the menu doesn't show up at all! What's going on here?

  • Site Index Portlet Installation Problem

    Hi,
    I had tried installing site index portlet in
    Oracle Application Server 10g Release 2 (10.1.2.0.2)
    After completing the installtion steps
    it is producing below mentioned log.
    But after i trying to logon into portal
    it is showing
    Servlet Error
    An unexpected servlet error was encountered.
    Please check the log file for more details.
    Any clue available ????
    Rgds
    Vijay
    Log file information
    SQL>
    SQL> @E:\site_index\schema\ptlsipi.sql
    Installation of Site Index Provider
    DROP SEQUENCE serial_order
    ERROR at line 1:
    ORA-02289: sequence does not exist
    Sequence created.
    Table created.
    0 rows deleted.
    Commit complete.
    Creating Site Index NLS Package
    Package created.
    No errors.
    Creating Site Index NLS Package Body
    Package body created.
    No errors.
    Grant succeeded.
    Installing the NLS Strings (English)
    Starting inserting the NLS Strings
    Finished inserting the strings
    PL/SQL procedure successfully completed.
    No errors.
    Creating Site Index Provider Package
    Package created.
    No errors.
    Creating Site Index Portlet Package
    Package created.
    No errors.
    Creating Site Index Provider Package Body
    Package body created.
    No errors.
    Creating Site Index Portlet Package Body
    Package body created.
    No errors.
    Creating Site Index Tree components
    Package created.
    No errors.
    Package body created.
    No errors.
    Grant succeeded.
    Grant succeeded.
    Registering the Site Index Provider
    Enter value for portal_schema: portal
    Registering Site Index Provider
    Site Index Provider successfully registered:478560949
    PL/SQL procedure successfully completed.
    Commit complete.
    SQL>
    ---------------------------------------------------------------------

    A few other options:
    - Do you use a language that can be used in the pagegroup? if not the select statement he uses will not find any data => try to switch to a language that was published for this pagegroup.
    - Just to make sure, can you make a select statement to the wwv_user_corners tabel from the schema in which you have installed the portlet?
    - dig into the html source code where you have put your menu on and try to get the url of the tree and open it(search render_tree_items), check if any values have been created for the menu.
    If this is empty you should try this select statement and try to find out what causes it not to give back any values:
    select level, siteid, id, title, parentid from wwv_user_corners t1
    where t1.siteid = '||p_siteid||'
    and t1.is_template != '||wwpob_api_page.PAGE_TEMPLATE_YES||' -- 0
    and t1.type not in
    ('||wwpob_api_page.PAGETYPE_TAB||' ,
    '||wwpob_api_page.PAGETYPE_MOBILE||' ,
    '||wwpob_api_page.PAGETYPE_NAV||' ,
    '||wwpob_api_page.PAGETYPE_CAT_PERS||'
    and t1.language = '''||p_lang||'''
    start with id = 1 and siteid = '||p_siteid||' and language = '''||p_lang||'''
    connect by prior id = parentid and siteid = '||p_siteid||' and language = '''||p_lang||'''
    order siblings by title;

  • Site Index Portlet Only Displays Public Pages

    We have installed Site Index Portlet 9.0.4.0. It works as advertised, with one exception. The tree shows only shows pages that have the box "Display page to public users" checked. If this box is left unchecked and view access to the page is granted directly to the user, the page is not displayed in the site index tree. Has anyone else gotten this to work?

    Yes, we are also having the same problem. I've also noticed that non-public pages will show up in the tree ONLY if you are the owner/creator of the page. It doesn't seem to look at any other group/user permissions.

  • File and directory names with Danish characters

    I have installed the Novell Client v2.0 for Linux on my Open Suse 10.3. The Client is connecting to my Netware servers (6.0 & 6.5) without any problems...
    There is one problem... Filenames and directory names with the Danish , & (ae, oe & aa), e.g the filename bger.doc (bger = books) is shown as b. and when clicking the file the file disappears from the file list. It seems to be the same problem with the German (umlaub).
    What to do?
    /Michael

    Originally Posted by J.H.M. Dassen (Ray)
    mimo <[email protected]> wrote:
    > There is one problem... Filenames and directory names with the Danish ,
    > & (ae, oe & aa), e.g the filename bger.doc (bger = books) is shown as
    > b. and when clicking the file the file disappears from the file list. It
    > seems to be the same problem with the German (umlaub). What to do?
    As far as I know, the Novell Client for Linux expects that file and
    directory names use the UTF-8 encoding and does not support a traditional
    8-bit encoding like ISO 8859-1. Try changing the encoding of file and
    directory names to UTF-8 as described in
    SDB:Converting Files or File Names to UTF-8 Encoding - openSUSE
    HTH,
    Ray Dassen
    Technical Support Engineer, EMEA Services Center, Novell Technical Services
    Novell, Inc. Software for the Open Enterprise Software for the Open Enterprise
    Seems a good hint. When I create a folder or file from within SUSE using an "Umlaut" everything is OK and NCL 2.0 displays them correctly as they are UTF-8 formatted.
    The proposed tool is no solution: one cannot convert folders or files that one cannot see (does it work for folders at all?). Maybe a windows tool would work because one could search for all files or folders with "Umlaute" and convert them. Other options?

  • Prevent using special characters in file and folder names?

    I've recently begun adding windows clients to my network. In doing so, I've found that on my file shares from OS X server, the windows clients are unable to see files and folders which have names containing special characters such as / ? < > \ : * | ”
    Unfortunately my accounting department has been creating files with these characters in their names for several years. I would like to find if there is a way to prevent them from using a defined set of characters in the file and folder names to prevent them from "accidentally" doing so in the future.
    I've found that by turning off streams support on SMB in OS X server, that my windows clients can at least see that a file or folder should exist, albeit with a corrupted file name. Removing the special characters from these names allows the proper name to become visible and the file accessible.
    Any info would be greatly appreciated.

    (_seb_) wrote:
    > Gary White wrote:
    >> On Sun, 19 Nov 2006 19:15:04 +0100, "(_seb_)"
    <[email protected]> wrote:
    >>
    >>> "ça alors: it's a déjà-vu"
    >>>
    >>> How can I encode this so it's valid as a
    directory name, yet can be
    >>> displayed as intended when the name is output to
    the page.
    >>> urlencode() does not do the job, neither does
    htmlentities()...
    >>
    >>
    >> What's wrong with:
    >>
    >> $l="ça alors: it's a déjà-vu";
    >> print urlencode($l)."<br>\n";
    >> print htmlspecialchars($l);
    >>
    >> Gary
    >
    >
    > I know that, but what is the name of the directory? It
    has to be a real
    > directory name, not a string stored somewhere.
    >
    > What's a valid encoding for a directory named "ça
    alors: it's a
    > déjà-vu"? I can call a folder like this on my
    Mac, but it won't work on
    > any server...
    >
    >
    >
    PS: basically it's not a url encoding issue.
    I can url encode "ça alors: it's a déjà-vu",
    and pass it in a url query string. But my issue is not
    with an url query string, it's with an actual URL, that is,
    the actual name of the directory. It
    can't be "ça alors: it's a déjà-vu". But I
    want to allow the user to name their directory like that
    if they want. So I need a way to encode this into characters
    that can be used for an actual
    directory on the server.
    seb ( [email protected])
    http://webtrans1.com | high-end web
    design
    Downloads: Slide Show, Directory Browser, Mailing List

  • Windows 2003 - create folder name with yesterday's date

    Hello friends..
    please advise,
    I want to create folder name with yesterday's date and then move yesterday's date files to this folder...so for example;
    if today is 2014_07_17 then create folder as below (2014_07_16)
    d:\test\214_07_16
    then move all files extension .txt from d:\test\*.txt to d:\test\2014_07_17
    thanks in advance...

    These ones may help.
    Use PowerShell to Create a Bunch of Folders Based upon the
    Date
    Using the Move-Item Cmdlet
    Regards, Dave Patrick ....
    Microsoft Certified Professional
    Microsoft MVP [Windows]
    Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

  • Site index portlet error

    <p>Hello,</p>
    <p>I have installed the siteindex portlet following the installation instructions in a Oracle Aplication Server Portal 10.1.2 and I receive this message when I try to include this portlet in a page:</p>
    <FONT CLASS=PortletText1>Error: El servlet ha producido la siguiente pila de errores. oracle.webdb.page.v2.MetaDataParseException: Block Attribute Parse Error: found 'n' after attribute char when expected '='84 : blockClass='oracle.webdb.page.v2.PortletBlock' blockId='73,44278' prevAttribute='T' : Page '73,36452'
         at oracle.webdb.page.v2.BaseBlock.throwAttributeParseError(Unknown Source)
         at oracle.webdb.page.v2.PortletBlock.parseAttributes(Unknown Source)
         at oracle.webdb.page.v2.BaseBlock.parse(Unknown Source)
         at oracle.webdb.page.v2.PortletBlock.parse(Unknown Source)
         at oracle.webdb.page.v2.PortletBlock.<init>(Unknown Source)
         at oracle.webdb.page.v2.PortletBlock.parse(Unknown Source)
         at oracle.webdb.page.v2.PageMetaData.parseBlock(Unknown Source)
         at oracle.webdb.page.v2.BaseMetaData.parseBlocks(Unknown Source)
         at oracle.webdb.page.v2.PageMetaData.<init>(Unknown Source)
         at oracle.webdb.page.v2.DataProcessor903.getPageMetaData(Unknown Source)
         at oracle.webdb.page.v2.DataProcessor903.process(Unknown Source)
         at oracle.webdb.page.PageBuilder.process(Unknown Source)
         at oracle.webdb.page.Main.doRequest(Unknown Source)
         at oracle.webdb.page.ParallelServlet.doGet(Unknown Source)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
         at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
         at com.evermind.server.http.ServletRequestDispatcher.invoke(ServletRequestDispatcher.java:810)
         at com.evermind.server.http.ServletRequestDispatcher.forwardInternal(ServletRequestDispatcher.java:322)
         at com.evermind.server.http.HttpRequestHandler.processRequest(HttpRequestHandler.java:790)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:208)
         at com.evermind.server.http.AJPRequestHandler.run(AJPRequestHandler.java:125)
         at com.evermind.util.ReleasableResourcePooledExecutor$MyWorker.run(ReleasableResourcePooledExecutor.java:192)
         at java.lang.Thread.run(Thread.java:534)
    </FONT>
    <p>Some idea?</p>

    Hi,
    I had tried installing site index portlet in
    Oracle Application Server 10g Release 2 (10.1.2.0.2)
    After completing the installtion steps
    it is producing below mentioned log.
    But after i trying to logon into portal
    it is showing
    Servlet Error
    An unexpected servlet error was encountered.
    Please check the log file for more details.
    Any clue available ????
    Rgds
    Vijay
    Log file information
    SQL>
    SQL> @E:\site_index\schema\ptlsipi.sql
    Installation of Site Index Provider
    DROP SEQUENCE serial_order
    ERROR at line 1:
    ORA-02289: sequence does not exist
    Sequence created.
    Table created.
    0 rows deleted.
    Commit complete.
    Creating Site Index NLS Package
    Package created.
    No errors.
    Creating Site Index NLS Package Body
    Package body created.
    No errors.
    Grant succeeded.
    Installing the NLS Strings (English)
    Starting inserting the NLS Strings
    Finished inserting the strings
    PL/SQL procedure successfully completed.
    No errors.
    Creating Site Index Provider Package
    Package created.
    No errors.
    Creating Site Index Portlet Package
    Package created.
    No errors.
    Creating Site Index Provider Package Body
    Package body created.
    No errors.
    Creating Site Index Portlet Package Body
    Package body created.
    No errors.
    Creating Site Index Tree components
    Package created.
    No errors.
    Package body created.
    No errors.
    Grant succeeded.
    Grant succeeded.
    Registering the Site Index Provider
    Enter value for portal_schema: portal
    Registering Site Index Provider
    Site Index Provider successfully registered:478560949
    PL/SQL procedure successfully completed.
    Commit complete.
    SQL>
    ---------------------------------------------------------------------

  • Site Index Portlet - ordering items ?

    Is there any way of ordering the items in a page group so that they display in a desired order in the Site Index Portlet ? I think they are displayed by creation date order as it is.
    Thanks

    Hi Rich,
    The source code for the SIP portlet is available along with the download. I dont think it should be too difficult to change the ordering to what you would like.
    thanks,
    Harsha

Maybe you are looking for