cstevensjr

Are you experiencing slowness just with ProcessWire or a particular installation? Do you have any other site installs that you can compare against?

I may be wrong, but the naming scheme you are using is more like the default profile for PW. If you were trying to do the delayed output, the instructions you referenced in the link are highly detailed on how to achieve that design. It also wouldn't hurt to have more detailed information about your installation (Front-end framework used, version of PW, PHP, etc..) and what you are trying to achieve. The code that you showed would output the text "test".

Support Forums are hard to maintain. There will always be an influx of new people with new ideas. Our challenge is to incorporate these individuals while teaching them good web development techniques. These people will be the next group of teachers about ProcessWire. @pwired makes some valid statements. I believe everyone should be heard, in a professional and mostly courteous manner. There will always be newbies that will challenge our patience, however we need to just remember that learning takes time. They are excited because ProcessWire is a fantastic development platform. We will have troublemakers join our group, however we need to not change who we are based on their need to make trouble and discord. There are great and extremely talented people from around the world actively participating in this forum. If we maintain our technical excellence and dignity, then it doesn't matter what a few idiots have to say. Anyway, once they see that we are about positive outcomes they will fade away. We should be striving to see everyone reach that initial "AHA" ProcessWire moment, no matter how long it takes. This is a great Forum and we collectively need to ensure that we keep it that way. Best Regards, Charles

Edit: Charles = cstevensjr Both are acceptable.

@kathep, I personally think that you ask very good questions. From what I have seen, you follow-up for clarity and contribute by articulating your thoughts.

@hellomoto has another thread going where I explained that the capabilities of 2.5.14 are not in his currently installed 2.5.3 version. https://processwire.com/talk/topic/8787-config-usertemplateids-anyone-implemented-this-so-far/

My setup is very different. I do all my web development work online using Dedicated servers. I create a development domain environment for each client and they have access to review the website work as it's being done. This works great for me since the transition from development to production is minimal. I brief each client on an at least weekly basis (online meeting, via phone or in-person) on the topics that are important to them. Each of my clients has 24 hour access to a customized project management website (Processwire based & still under constant development: i.e. alpha status). I make use of the client project website, Evernote (shared notebooks) and Dropbox (shared folders) to maintain all client related work and documentation. I work to ensure that the 3 systems stay linked together in a cohesive manner. A majority of my clients are not associated with any web development work, however I make sure they are familiar with ProcessWire through the client project websites. They get to see and work with the front-end/back-end (Admin) sides of ProcessWire on a constant basis.

Features that are released for the 2.5.14 version are not going to work in your 2.5.3 install. Here http://processwire.c...updates-2.5.14/ there is a quick tutorial on setting up an alternate user template and parent. You would need to first update to Development version 2.5.14 to gain access to these features, as they are introduced starting with this version.

A very nice website. Welcome to ProcessWire!

In the cPanel CRON job documentation: In the COMMAND text box is where you enter the correct command syntax EDIT: You got it! Welcome to ProcessWire.

Is that the screenshot of your CRON settings? Please take a look at the following documentation: https://documentation.cpanel.net/display/ALD/Cron+Jobs

On my CPanel I have things listed as following: curl -sS "https://yourdomain.com/?hash=0ae6cff16bc1e1ad77c2706acaf0358b2848395g" > /dev/null This works for me.

Welcome to ProcessWire, @hellomoto. Have you taken the time to read up on the available ProcessWire documentation? I hope you know that you can also do a Google search of the forum and get many of the answers that you have been asking. Have you tried out the Skyscraper demo yet? Do you fully have a good understanding of ProcessWire fields, templates and structure? I may be wrong (and please forgive me if I am), but you seem to be running before you have learned to walk. PW is a great platform, however everyone needs to take time to digest the many different issues that come with learning a new system. This forum is a remarkable place, where there are many people willing to help you. I am only bringing this up because I believe that if you spend a little more time researching what's already available, you will find the answers to most of your questions. I would think relating users to other pages would be a fairly common requirement too, You are indeed correct about the above statement. There is a multitude of documentation and forum posts that detail how this works (to include examples). I wish you the best with becoming familiar with ProcessWire. Best Regards, Charles

Ok, then I would then look at the php mail function on your server. I believe this module doesn't make use of enhanced PW capabilities for email sending. It would be great if the wireMail function could be used for sending emails instead of the php mail function. This way people would be able to use it together with their favourite mail extensions. For example with SMTP support: wiremail-swiftmailer or wiremailsmtp

but it doesn't seem to work (I've used my @gmail.com as emailTo) Gmail doesn't allow you to send an email from yourself to yourself, unlike other email platforms. The message gets sent but you don't receive the copy, since if's from yourself.

Without looking too hard, I would suggest you upgrade the XAMPP (Current version is 5.6.3, so what you have is old and may not still be supported). The PHP minimum for PW is 5.3.8, however it wouldn't hurt to have a more recent version.

Any body have an explanation If somehow you are dealing with ioncube, then this was not a PW related issue. Glad you finally got it working.

Can you please answer the following: What is the structure of your site? Describe what fields you are searching on? Give a few examples of situations where the search fails. Are you able to get any search results at all? What program you are saving your edited copy of the search.php file in? Versions of PHP, MySQL and PW. Is this a Local install or an online instance? Platform where you are having this problem. Have you tested this on any other platform? Have you tested this on any other install besides the Blank profile? It would also be informative if you can state in what file are you calling the search form? In the site default profile, the search form is listed as <form class='search' action='<?php echo $pages->get('template=search')->url; ?>' method='get'> <input type='text' name='q' placeholder='Search' value='<?php echo $sanitizer->entities($input->whitelist('q')); ?>' /> <button type='submit' name='submit'>Search</button> </form> in the _main.php file. Have you used the same form syntax to call up the search in your install? If not, could you please list your code. I know these are a lot of questions, however answering them will help someone to help you find a solution to your problem. Best Regards, Charles

From what I know, you need to have the correct fields you want to search on listed in the search criteria to be successful. I believe the default criteria in search.php for the site-default profile is: $selector = "title|body~=$q, limit=50"; This works great if you are only searching for words in the Title or Body fields. However, If you have any other fields that you want to search on, they need to be added to the search criteria. $selector = "title|requestor_name|requestor_comments|summary|body~=$q, limit=50"; When I first started with PW, I didn't understand this and hence could never get the search results I was looking for. One day the light went on and I haven't had a problem with searching since. I don't know if this is the issue that you are having, however I just thought I would mention it as the default search file works like a charm.

I may have read this wrong, at first you said (A listing may not have children.) Then you say I can edit the listings, but there's no "New" link to create any? I believe you can't create a child if you have already stated that there will be no children under that template.

Happy New Year from Banning, California

I finally got around to do some thorough testing of the new capabilities. I tested on Customized Email, Gmail, Yahoo and MSN (Outlook) and everything works great. I especially like how you treated the attachments and split out the From and email address. Thanks again for all of the enhancements.

FYI, I had a problem with the body text not showing up. I looked at your code and ended up doing a diff to see what was going on. Somehow the following code was dropped from the update: $page->{$category->bodyField} = $body; I added this code to the recent update and then the body text showed up again.

Ok, I first had the From field mapped to a PW Email Field. My Yahoo account has the email and name both mapped to my email address, hence that's why the email address showed up. I then tested on Gmail and MSN and nothing showed up. I then understood the problem and changed the PW field to a text field and then the name showed up when importing Yahoo, Gmail and MSN emails. Operator error on my part. The Name field works great.

Adrian, From the limited testing I have done so far, it is giving me the email address. I need to test from other email providers other than Yahoo to see what shows up. Either way, this is more than what I had yesterday. I believe that the more functionality that this module has (being able to map email metadata with actual PW fields), the better it will serve the diverse needs of the PW community. I also hope we can get these changes merged with the published version on the PW website. Thanks again, as you have made my day. Best Regards, Charles