Jump to content

Reid Bramblett

Members
  • Content Count

    43
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Reid Bramblett

  • Rank
    Jr. Member

Profile Information

  • Gender
    Male
  1. Thanks, Robin. Works a treat. I had tried fiddling with the number_format as well, but didn't really understand it. I did, however, go back and tweak the regex statement so that it would catch single-digit amounts, too, as well as amounts with or without a two-place decimal amount (the "cents").
  2. I want to use this lovely little converter to search a given textarea field for all mentions of currency amounts, convert each of those to another currency, and then show both. In other words, taking: and turning that into: (The usd amount, obviously, would be filled in by the converter.) After dozens of code variations and attempted angles of attack, I feel like I am close with this—but it is not quite working. $cc = $modules->get('ServiceCurrencyConversion'); $text = $page->body; $regex='/\x{20AC}\d+(\.\d{2})?/u'; $text = preg_replace($regex, '$0 ($' . $cc->
  3. I am having the exact same problem. It's been almost a year since this thread began; any solutions?
  4. The error logs have nothing in the past three days. There's just that one line that pops up at the top of the screen every time I try to save a page with an image field: I am afraid I don't understand enough about the inner workings of PW to know why this field and no others is throwing an error. The only other bit of intel I can think to provide is that I am using the Type "CroppableImage" for the images field (and I have the most up-to-date version of that running).
  5. OK, so that was fun. I decided to try the PW3 upgrade, got it working swimmingly on the local server, but when I pushed it live it all went haywire (multiple reloads in admin did not do the trick). Spent several hours trying to get it to work, then several more trying to flush out the system and replace it with the 2.7 that had at least been mostly working. Now I am back almost to where I started—though I managed to fix one of the two errors. I got rid of... ...by simply creating an empty MarkupCache directory in that spot and the warnings went away. How
  6. Frankly, I was so close to launching I didn't want to run the risk of having PW 3 break the site and setting me back. I just wanted it out there and live before I started fiddling in dev with a new PW version.
  7. Plenty of disk space. The permissions really don't seem to be the issue. I changed the handful of 777s to 755, and no dice. (The only directory/file permissions that aren't 755/644 are the session files within site/assets/sessions, all of which are 600 and unchangeable). For the record, I am running PW 2.7.3
  8. Thanks for the quick reply again, Rick, but that doesn't seem to be the issue. It looks as if every directory/file is at least at 775/644 or better (a few are even 777). I did not actually check every single one, because I am using a hierarchical interface rather than some kind of Terminal/SSH window (I do not really understand those, and am worried a typo will wipe out everything), however I checked every directory, sub-directory, and file (or exemplar thereof). Any other advice?
  9. Trying to work the kinks out of my first live PW site. Most of it displays beautifully on the front end (save, oddly, one rather important page throwing a 404, but I'll try to troubleshoot that once I get this bigger issue resolved). I can also log into admin and browse the pages tree and open pages in edit. However, whenever I try to save a page (whether an existing one I have edited, or a new one I am attempting to create), I get the following error message: In addition, if the page happens to contain an image field, prior to that "unable to create path" error I also get:
  10. I love PW. I post a question, take a lunch break, and the answer arrives! I guess my suspicion about the name of the .htaccess was correct—and that fixed it.
  11. OK, I did my due diligence of searching for an answer for a full 24 hours before giving up and posting this plea. I have just uploaded my first PW site to a live server, but can only get the homepage to work. Clicking on any link to any other page results in the following error page (with the subpage link after "URL" properly filled in with whatever page it was I was trying to reach, in this case /places/): I take it from others who have had this issue is that it has to do with a configuration in the htaccess file. The solution for others seems to have been uncommenting
  12. Beauty, Netcarver. Just the ticket. (And I had already resigned myself to working with leaflet's limited color palette to approximate the color scheme I'm using on the site.) Thanks so much for this. Does in a few lines of code what used to take me ages to create by hand. Loving it.
  13. This may seem simplistic, but how do I make a map where existing fields on the pages define the marker settings? In other words, rather than creating separate new fields on the page template for marker_icon and marker_color (and then laboriously having to fill them in each time), how I can use an existing field, and then merely provide some code denoting the corresponding changes I would like to the marker options. For example, for a travel site, each page has a "category" field (sleep, eat, see), and I would like that field to automatically determine the marker color and icon (anything
  14. Sebii was right! Turns out there was a smack-myself-on-the-head spacing typo in a separate template dependent upon this page, that only applied to this page, and it did have to do with cat_rank (as a search parameter). I had, in the string of parameters, "cat_rank>0 ," (with a space between the zero and the comma. Removed the space, problem resolved itself. (Since I hadn't touched that template in ages, though, I'm still confused as to why it was suddenly a problem and not before. Maybe PW is just getting better at rooting out bugs.) Thanks for all the help!
  15. Hmm. I ran the updater and ticked the box to replace it, but I also don't see an old one backed up. To be sure, I just downloaded afresh the entire zip file from the Processwire site, looked at its index.php, and it seems identical to mine (and runs to 251 lines—well, 249 plus two superflous carriage returns at the end).
×
×
  • Create New...