We launched new forums in March 2019—join us there. In a hurry for help with your website? Get Help Now!
    • 27330
    • 884 Posts
    We have on my site a section for my clients. each one of them get’s his own page which is restricted to him only. On these section we use a template which have a table with all the docs we need regarding his project such as proposals and blue prints etc.
    I can create whatever TV’s I want, or simply use the main content of the page to write whatever message I want. If I wanted to allow them to reply I could use Jot for comments.
    If I wanted to show specific info about them which are under Web Users>user name>General I could use this http://modxcms.com/extras/package/480

    If you don’t need to let the end user edit his own info or anything fancy I don’t see the need for webloginPE,
    If you want specific custom fields you could always use TV’s for the clients section template.
    But this is just my opinion.

    For your problem before you go and change the DB, AFAIR the custom fields worked fine with RTE. Does it save the data if you only set the TV to text and no widget?
      • 15003
      • 85 Posts
      sinbad --

      I’m using WebLoginPE so that the users can update their contact info and password. I have it in place and it’s working fine.

      I can create whatever TV’s I want, or simply use the main content of the page to write whatever message I want
      I find this statement confusing. It sounds like you’re talking about a page in the admin area, but if you write info in the main content area of the page it will be reflected on that pages for all users, not just a specific user.

      ...so I’m fairly new to CMS systems and I think I need to be walked through the concept:

      I understand the idea of creating a new Template that hold’s whatever TV’s I want and that I can include content and a form in the "Document Content" area. And I’m assuming that this page, using something like MemberCheck, can only be seen by a logged in site admin or manager. On this page they can choose a client from a drop down list and then edit or add info into a RichText <textarea>. I would then pull that info into each users view-profile page.

      Is a basic version of what your talking about?

      I was actually avoiding having to do this and thought I could take a short cut and let my client add specific user into through Create/edit web user interface.

      I have other questions, but I want to make sure I understand the correct direction to go in first.
      I appreciate your patience:-)
      ~Jules
        • 27330
        • 884 Posts
        no, we do the edits from the manager. I don’t need front end interface for that. My clients can change their password with weblogin snippet.
        but since you want to allow them update their profile so you need webloginPE and the whole deal. which bring us back to my previous Q, does the data stored if you using text only for the TV option?
          • 15003
          • 85 Posts
          does the data stored if you using text only for the TV option?
          I don’t understand what your looking for.

          If I use the text "Hello World" for the default value of the TV [*comment-RT*] and place this TV in the document content "Hello World" shows up in the browser window.

          The [*comment-RT*] TV at the bottom of the Create/edit document page under Template Variables shows the default value "Hello World".

          If I replace the default value to: @SELECT `comment`FROM `modx_web_user_attributes` WHERE internalKey=’1’ it shows up as the default value at the bottom of the Create/edit document page under [*comment-RT*] but in a browser window I get the word "Array"

          Is this the info your trying to get from me?
            • 9207 ☆ A M B ☆
            • 2,475 Posts
            Very good points... It’s a pain to have 2 interfaces...

            I have never hacked the core... I’m too busy hacking my own code.

            Man, that’s a tricky one... I can think of a couple contorted ways to do this, but not an elegant way...

            I think either hacking the core or relying on the phpMyEdit to handle ALL the user creation / editing aspects are probably your best bets to preserve a single interface for your client.