MindFull

Members
  • Content count

    98
  • Joined

  • Last visited

  • Days Won

    1

MindFull last won the day on April 7 2014

MindFull had the most liked content!

Community Reputation

106 Excellent

1 Follower

About MindFull

  • Rank
    Full Member

Profile Information

  • Gender
    Male
  • Location
    VA

Recent Profile Visitors

1,899 profile views
  1. ################################################################################################# # START PROCESSWIRE HTACCESS DIRECTIVES # @version 2.3 ################################################################################################# ... # ----------------------------------------------------------------------------------------------- # Access Restrictions: Keep web users out of dirs that begin with a period # ----------------------------------------------------------------------------------------------- RewriteRule "(^|/)\." - [F] Eeek! - My PW 2.3 is showing lol! I have go to remove that from my Notepad++ cache
  2. Absolutely loving this! The tables look great - way to to put PW to work!
  3. I've seen the .well-known directory with hosting providers that offer cPanel accounts with the AutoSSL feature turned on. Both LetsEncrypt and Comodo cert renewals use the folder to install and replace soon-to-expire SSLs. Depending on your hosting provider's configurations, even self-signed SSLs may get updated. BTW: For those that chose to use AutoSSL, Processwire's .htaccess config prevents reading of .txt files and access to directories beginning with periods so those would need to be turned off temporarily to allow the cert to be installed. Otherwise, PW will issue a 403 each time AutoSSL attempts to access the directory/file. Then, the SSL will expire and piss everyone off until it's fixed. But that's no fault of Processwire - It's better to keep those things in check then to let hosting plugins silently do whatever they want.
  4. Then don't save it No, really though, if you want you can just delete/clear the field before save.
  5. That's great to hear! It makes me want to give it a go just to see how it compares with my vagrant/vb box config. More speed = more better lol.
  6. Just an idea: use PageTable. Maybe use a template for artist that has Artist_firstname and Artist_lastname, etc. Then, a pageTable called Artist_pageTable that uses the artist template. Also, create a template called Artist_works with the associated work fields, including the Artist_works_inventory_no. Then create a pageTable called Artist_works_pageTable that uses the Artist_works template. Since everything's a page, you could do this: $pages->get("template=artist,Artist_firstname=$firstname,Artist_lastname=$lastname")->children("Artist_works_inventory_no=1")->count();
  7. The repeaters are nested so you'll need to approach this differently. In your page tree, you'll see that the repeaters are not true pages of your Artist page. If you look at settings of the repeater fields you created, you'll see they have templates and parents that belong in then Admin/Repeaters area. If you must use repeaters like this (which I don't think you do) you'll need to target the repeater templates/parents. Since your attempt shows that Artist_works_inventory_no is not unique, you could try: // get ID of repeater with artist that matches the first/last name provided $artistRepeaterID = $pages->get("template=repeater_Artist,Artist_firstname={$firstname}, Artist_lastname={$lastname}")->id; // repeaters have names like for-page-someID, check your page tree to see what I mean $artistWorkParent = "for-page-".$artistRepeaterID; // Find the matching children that have the inventory id and count echo $pages->get("name={$artistWorkParent}")->children("Artist_works_inventory_no=1")->count(); Personally, I think this approach with nested repeaters could be reevaluated. Many you can explain what you're trying to accomplish?
  8. I think so too. If the inventory number is unique for all art work, you could use: echo $pages->count("template=repeater_Artist_works,Artist_works_inventory_no=1"); The repeater before Artist_works comes from PW adding before storing the repeater field in Admin/Repeaters
  9. Maybe you can show us what you've tried? I just copied/pasted Soma's example and the core of it stills offers a starting point for using PW core inputfields in custom forms. Here's how the result looks: This is with the code Soma gives for the form and the head.inc which he gives in the mentioned thread. You'll have to make it functional for your needs but it gives you a starting point.
  10. Congratulations! It gets easier on each iteration (no pun intended)
  11. Just curious, is there a particular reason to why you use opening and closing php tags for each line of code?
  12. Not to nitpick, but remember that $pages->find will give you a pageArray so it is possible that the $store->title might not work how you'd expect. If another child of Deals exists, then you might run into some errors. It would be better to use either $pages->findOne or $pages->get. If you anticipate that Deals might have more child pages, I would suggest expanding the selector as well.
  13. Wow, that's strange that they would do something like that. In ProcessPageEditLink.js, I see this // avoid adding scheme if we already added it before and user removed it if ($this.attr('data-ignore') == domain) { // do nothing } else { $this.val('http://' + val); $this.closest('.InputfieldContent').find('.notes').text('http://' + val); $this.attr('data-ignore', domain); } So it looks like if you delete the http:// once or twice, it should stop auto-filling.
  14. That's weird but it looks like you're working out of two different directories for the install. You have a _tmp and a tmp. Maybe double check the install directory and make sure that the htaccess file, and wire & site directories exist alongside index.php. Which version of PW are you using?
  15. Just curious, if it is an external link, why would you want to remove the http:// ?