Jump to content

Lance O.

  • Content Count

  • Joined

  • Last visited

  • Days Won


Everything posted by Lance O.

  1. The following site developed in PW loads very slowly. I updated PW to 2.7.1, but I don't know if that is the culprit, since the client told me that the site was loading slowly for a couple of days before the upgrade. The site is hosted on Media Temple Grid and is using PHP 5.5.21. Both the public site and the PW admin load slowly. Media Temple has suggested adding a MySQL GridContainer. Any ideas? This is the first time I've encountered this problem, and I honestly don't think PW is to blame. Currently, I don't have caching enabled, but even if I did, that wouldn't help the PW admin. Anyone else hosting on Media Temple? http://richrosendale.com/
  2. It looks like setting up the Source URL with the additional code works. (It doesn't look like we need to add the additional code to the page url.) Thank you for your quick response! Client is happy and has restored faith in PW and Jumplinks.
  3. I am using Jumplinks for one of my clients. We have set up a number of redirects to monitor several campaigns we have in place. For instance, we have links like this: http://website.com/bioh that redirect to actual pages in the site: http://website.com/biohealth/ The original link is being used in Google AdWords. AdWords is adding a Google Click Identifier (gclid) to the url, so when a user clicks on the link, it actually appears like this when they visit the site: http://website.com/bioh?gclid=CPaHlL3_jckCFdc9gQod4xEB4g The problem is that the link with the gclid parameter is returning a 404 error. Jumplinks doesn't appear to recognize when a parameter is appended to the url. Is there a way to prevent this, or perhaps I didn't set something up correctly? Any advice is appreciated. I'm using Jumplinks 1.3.1 with ProcessWire 2.6.1.
  4. Thanks, all. I'll check out the modules mentioned above.
  5. No offense to the developer of FrontendUser, but I'm cautious about using modules that provide functionality that are core to a project's success. I came from the WordPress world and was burned more than once on plugins that were no longer supported by the developer. I'm at the point where I would rather spend $100 on a module and be confident that it is going to be supported rather than using a free module that may later be abandoned. Yes, basics like registration, login, change password, email address, name, and upload image would need to be supported, allowing users to edit their profile using a custom front end template without having access to PW's back end admin.
  6. I'd love to see the next Pro module provide an easy way for front end visitors to register an account and edit their profile.
  7. My preferred approach is to create a high level "Slideshows" page. Then I will create a parent "Slideshow" page and add individual slides as child pages. On the page where a slideshow needs to be assigned, I create a Page field that allows for a single slideshow selection. Using repeater fields is a bit limited in that you have to completely delete the slide from the slideshow if you no longer want to use it. Some of my clients want to unpublish a slide and then use it again in the future. Using pages as individual slides provides them more flexibility, and using pages as slideshows allows them to create a variety of slideshows that can be swapped out. For example, a client may want to change Home page slideshows on a seasonal basis.
  8. I like ProcessWire, and I've used it on almost every project in the past three years. But to state this in the way that you have is borderline trolling. You are of course entitled to your opinion, but in my world, things aren't as easily defined in black and white. And they aren't for my clients, either.
  9. Yeah, still not helpful for my (potential) clients. The default CMS in my locale is WordPress. Everyone here knows what WordPress is, but 99% haven't heard of ProcessWire. So sometimes selling ProcessWire as a solution is a difficult task, despite ProcessWire's obvious advantages. Potential clients that are on the fence will usually do their own research on the ProcessWire site. Providing release dates of previous versions in the "About" section of the site seems like a logical location for this type of information, since that is where most of my clients end up first. I'll also add that one of the criticisms of WordPress is the frequency of the updates. Clearly ProcessWire isn't updated as often (which isn't a bad thing). Wouldn't making this information easier to find be to ProcessWire's advantage?
  10. btw, I vote for an informational page similar to the following (maybe linked from the public Road Map), so that when a visitor is investigating ProcessWire and wants to know the frequency of previous updates, they are able to find it without having to perform a search in the forum or visit another site. https://codex.wordpress.org/WordPress_Versions
  11. Thanks, that helps! Looks like there has been a public release at least twice a year and within about 8 months of each other.
  12. Is there a page that lists all of the release dates for previous versions of PW?
  13. @renobird Your approach sounds simpler than creating a front end system. I'm curious to know: Did you create a front end registration form that adds the user to PW, or did you add users manually? When a user has only page-view and profile-edit permissions, the landing page they are taken to once they log in is a blank page with a "Continue" link to the site's Home page. Did you somehow add another page to the admin? Did you create a new PW Admin theme? I'd love to have more insight on your approach.
  14. Sorry, this project never got off the ground, but I do have a personal project planned where I would use similar functionality. I'll try to report my findings here when I find time to work on that project.
  15. By chance, this same error just occurred on another site I am developing. Again, manually setting parent_id to 0 in the database fixed the problem. Glad to see that you found the culprit. Looking forward to seeing a fix in the next release.
  16. This is in response to the following posts: https://processwire.com/talk/topic/5083-possible-bug-page-fieldtype-with-custom-selector-to-find-selectable-pages-returns-error-while-saving-page/ https://processwire.com/talk/topic/5683-inputfield-page-with-selector-rolesrole-page-1022-is-not-valid-for-field/ I am currently working on a site where I am using a Page field to assign multiple "products" to an individual "part". The "products" Page field stopped working recently and instead produces a "Page {ID} is not valid for {FIELD}" error. (Unfortunately, I'm not sure when it stopped working, but a design partner reported it to me today.) I created a second Page field that used the exact same settings. The second Page field worked with no problems. When I exported both fields to compare them, I noticed that the original Page field had a parent_id of 1052 assigned to it. When I manually changed that parent_id to 0 to match the working Page field via phpMyAdmin, the original Page field started working correctly again. Below are two exported fields. The first ("products") is the Page field that was giving me errors. The second ("products_test") is the test field I created that worked with no problems. I looked in my database and did not find any record of 1052, so I can only assume that it must have been a page that was deleted at some point. If it was deleted, then perhaps that id value wasn't removed from the Page field at that time? { "products": { "id": 147, "type": "FieldtypePage", "flags": 0, "name": "products", "label": "Products", "derefAsPage": 0, "parent_id": 1052, "labelFieldName": "title", "inputfield": "InputfieldAsmSelect", "findPagesCode": "return $pages->find(\"template=product,sort=title\");", "allowUnpub": "", "collapsed": 0, "showIf": "", "columnWidth": 100, "required": "", "requiredIf": "", "template_id": "", "findPagesSelector": "", "defaultValue": "", "addable": "" }, "products_test": { "id": 172, "type": "FieldtypePage", "flags": 0, "name": "products_test", "label": "Products (TEST)", "derefAsPage": 0, "parent_id": 0, "findPagesCode": "return $pages->find(\"template=product,sort=title\");", "labelFieldName": "title", "inputfield": "InputfieldAsmSelect", "allowUnpub": "", "collapsed": 0, "showIf": "", "columnWidth": 100, "required": "", "requiredIf": "", "template_id": "", "findPagesSelector": "", "defaultValue": "", "addable": "" } }
  17. Thank you for the quick responses! It does look like eAccelerator was the issue. It has been removed and replaced with APC and all is working well!
  18. I've made a copy of a site I've developed and installed it on a subdomain of the original domain. Then, I updated PW to 2.5.3, replacing the htacess file, index.php file, and wire directory. When I visit any page of the site, I receive a 500 Internal Server Error. The error log includes the following error: 2015-03-18 12:00:14 ? http://beta.domain.com/?/ Error: Invalid opcode 153/1/8. (line 28 of /home/user/public_html/beta.domain.com/wire/modules/Session/SessionLoginThrottle/SessionLoginThrottle.module) I've tried the methods on this page, but with no luck: https://processwire.com/docs/tutorials/troubleshooting-guide/ The server is using eAccelerator, if that matters. Any insight is appreciated.
  19. @adrian Just sent you a Dropbox link. Thanks!
  20. I just came across this same issue with PW 2.5.3. When SVG images are uploaded, PW stalls and won't create the thumbnail image. When I add the dimensions to the SVG file as suggested, the thumbnail image isn't generated and won't properly display on the public site (broken image shown in both cases). :-(
  21. I just discovered that if you create child pages of a parent page, then decide to add a PageTable field that includes template of the existing child pages, those child pages won't be available to add to the PageTable field on the parent page. In other words, if you are going to use a PageTable field, it appears that you'll need to make sure you create this field before you start adding child pages.
  22. Ah, I see it now after a bit of testing. Thanks for the insight and quick response!
  23. @Macrura Thanks for your response. Your examples help me understand when to use PageTables. You mentioned that "you can add pages not through the page table, and it will pick them up and ask you if you want to add them." What are you referring to here?
  24. I was going to start a new post but will piggyback on this one since my questions are related. As Ryan has stated previously: "PageTable lets you choose where [pages] should live, whether as children of the page being edited, or as children of some other parent page you designate." Can someone elaborate on the pros and cons of storing pages as children of the page being edited vs. children of some other page? I also understand that no matter the location of the child pages, additional child pages can only be added by using the PageTable field that has been set up. Are there some cases where it is better to hide stored pages under some other page to prevent confusion (from the client) when editing? It would also be helpful to know what types of data are most appropriate for PageTables. For instance, instead of using a repeater field, would the use of PageTables be more appropriate for PDF files that need to include additional fields, such as description or category?
  • Create New...