hollyvalero

Members
  • Content count

    26
  • Joined

  • Last visited

Community Reputation

1 Neutral

About hollyvalero

  • Rank
    Jr. Member
  • Birthday 09/14/1962

Contact Methods

  • Website URL
    http://hollyworks.com
  • Skype
    hollyvalero

Profile Information

  • Gender
    Female
  • Location
    Maine

Recent Profile Visitors

482 profile views
  1. Yeah, I think you're right. Just need to mimic the final destination... domain or subdomain for those that will be at the root. Or, identical folder name for those that will be in a subdirectory.
  2. ^^ btw, I did come up with an idea that would work... for websites that are either redesigns or brand new, I've designated an unused domain, activated it, and that will allow me to build at a .com address, export the site profile, and import it to another root level address. An addition to export site profile would be ideal, but this will work in the meantime...
  3. Yeah, trying to avoid further obfuscating DNS stuff, since that's the kind of thing that inevitably falls through the cracks later... no one remembers... the site grows big... It's not a huge site and grepping out all the paths will not take more than maybe an hour or two... I think. I'd rather do it now, before it gets bigger... Just wondered if there was a way to establish the root path within processwire. This is also helpful for developing a new site at an existing server... you'd want to build in a separate directory and move it up one while the current site is live and uncompromised. It's an administrative detail that always pops up in redesign. It would be the kind of thing that -- if it was part of Export Site Profile? Well, that would take care of it... if you could say "reset root path to..." with a domain name or domain.com/directory/path ...
  4. I have a website on a shared server that I use to store a few sites. My active domain is at the top. The new website domain hasn't been activated yet, but the path would be something like: myactivedomain.com/newdomain.com/ and once the DNS is flipped, just newdomain.com/ As I am building and adding a load of PDFs, all the links default to /newdomain.com/site/assets/files/etc... This isn't migration, but a DNS activation. Once that is updated, I'm still going to have a bunch of /newdomain.com/ links in there to pages, pdfs, images, etc. Before I resign myself to grepping out page-by-page all the "/newdomain.com/" references I thought I would see if there's a way to update these automatically in processwire but I'm seeing stuff on migration... stuff in the rich editors about correcting links, but I don't see anything that covers this. Is there a way to do this automatically? Via module? I didn't see anything in the config file... but would be grateful to anyone who can shed some light...
  5. I'm don't know how to implement this. Does every input field in the form need to be replace with a $variable . So the username field: <label class='label' for='username'>Username</label> <p class='control'> <span class='help is-info'>Please ensure your username contains <b>no spaces</b>. </span> <input type='text' class='input' name='username' value='{$v}'> </p> Does the entities string go before or after the form entry above? Do I batch all the sanitizer entries first? $v = $sanitizer->entities($input->post->first_name); Further down I am creating a user. Does this: $u->name = $sanitizer->username($input->post->username); Need to be changed to: $u->name = $sanitizer->username($v); If I can figure out the order for one field, I can apply it to all of them.
  6. Yeah, I could probably do that... I'm going to install Front End User at another copy of PW... see how that looks. Save this for my plan B. Thanks!
  7. uh, yeah.. that. Maybe someday. I am still in the beansprout/newbie phase.
  8. I'm running the latest version of PW, but if the only problem is the PW nag? I think I'll export the site profile, load it to a second spot and try front end user... with the added js/css for the field validation and see if it works. If it does, then we're all set. I also looked at the subscribers module ... that too seemed to be in alpha :-D ... I'll try Front End User first.
  9. I read through the multiple parents post. All my users basically enter the same 6 fields. They get assigned one of two roles depending upon whether they are just subscribing to content, or contributing content. I tried creating a user registration form... got it to create (albeit missing data, no follow up page, and ugly) to access > users ... but I'd need it to also notify the admin that a new user is waiting.
  10. I am about to ask a big, stupid question... having gone through 50 pages of user, login, registration stuff. I can easily create a form - or use formbuilder - to create a simple registration form for a couple levels of users (roles = subscribers, contributors) and I can easily send those entries to a page structure like Pages --- Users ------Subscribers -- Bill Smith, etc. ------Contributors -- John Jones, etc. This creates a directory of pages, assigned roles, and page access based on role, but this doesn't put those people into: ACCESS > USERS > My user data lives in Admin > Access > Users -- not in the document tree. If I want to have user accounts, doesn't Bill Smith, in the example above, have to be in both locations? Or, at least Admin > Access > Users? This is a conceptual problem, not a code problem... as a new user of PW, I don't know where my logged in users are supposed to live -- and if I use a form, how to get them there.
  11. This is exactly what I am doing... and I am using your formbuilder. I have a couple of registration forms - one shorter, one longer. The submissions are tagged as either subscribers or contributors and sent manually, to the document tree where I created: users --subscribers -----name --contributors -----name Contributors have access to the submission form pages that work like the example you cited to send data but not edit. Subscribers have access to view full detail pages, but they don't submit anything. Getting these entries into Admin > Access > Users is the question. It seems that users should be managed through this internal function since that provides login, reset password, etc. And in the back end, I can always add users manually, but I'm not sure (read: clueless) as to how to get those three fields: email, name, roles from the collected form entry into users...
  12. YAY!! That worked!!! Thank you!
  13. So this gives me: Call to a member function first() on a non-object (line 7 -- which is the line: $img = $image->first()->size(320, 180)->url; And most of my errors seemed to be like this. The field is a single image field, not a multiple image field.
  14. ** Actually the field is a single image field called "image" ... used for news features that have one teaser image...