Leaderboard

Give this module (attached) a try. To install, upload into /site/modules/ServicePinger/ServicePinger.module. Go to your Modules menu and click "check for new modules". Click install for ServicePinger. The module configuration screen has a textarea input where you can put in all the service URLs you want to ping. I recommend pinging one of the services that pings others, like pingomatic or weblogs.com, rather than trying to make this module do all of them. Actually, those are the only two services I've tested this with yet. When you install, it creates a new field called "pinger". Go and edit any templates you want to use it on and add the field "pinger". In your case, I'm thinking you'll just add it to the "post" template. Now edit a page with that template and see the "pinger" field you added. If you want it to ping those services, check the pinger box and save. You might want to test this out on one of your smaller sites first before migrating to your main site, as I put this together quickly and haven't yet tested it a lot. But I'm planning to add a README file and maybe a couple other details and then add it to the modules directory soon. ServicePinger.module

Ok there you go. Just added a new module to ModulesManager 2.1.0. You'll just need to update the ModulesManager, after that you'll find the new module ready to install. Modules Manager Notification 0.1.0 Sends out update information for installed modules to an email This module required LazyCron core module installed Note this is something you want to run like once a week When the lazy cron is running the request will be blocked for a few second, this is currently due to how the lazy cron works. Maybe we will be able to optimize this in future. After install you need to define the interval, an recipient email, subject and optional a "from" email address. There's also a checkbox to activate/deactivate the module running the lazy cron job. Note that this requires someone to hit your website (or admin) to get executed, so interval times can vary. It will then refresh the module feed from modules.processwire.com on your installation and check for new modules. If any found it will send out an email notification to the email specified in the form of: Found following updates for installed modules: Module: TextformatterHannaCode v0.1.4 Found new version available: v0.1.5 More infos at: http://modules.processwire.com/modules/process-hanna-code/ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– Module: InputfieldCKEditor v1.1.3 Found new version available: v1.1.4 More infos at: http://modules.processwire.com/modules/inputfield-ckeditor/ –––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––– It will also save a notification log modulesmanager_notification_log.txt with an entry when the lazy cron was executed in your site/assets/logs/ folder.

I realise that Marty and many others fully understand the issues here, but for anyone else with similar problems, here it is in a nutshell... PW selectors use mySQL fulltext indexes (indices? I'm never sure) mostly, as they are very fast. However Fulltext indexes miss out some common words (stopwords) because they are too common to influence search results meaningfully for the most part. And Fulltext indexes ignore words shorter than 4 letters, unless you have enough control of the server to change that default behaviour. (Think VPS or better.) However PW's %= selector operator uses mySQL's LIKE operator, which while slower than a fulltext search, is still very fast (certainly on fewer than several thousand records) and isn't restricted by stopword lists or word length.

No, that's normal. Read ryan's post about it here: http://processwire.com/talk/topic/2387-the-structure-of-fields-and-templates/?p=22762 Basically, since any field can be used in multiple templates, you can't simply have a table for each template with the PW fields as mySQL table fields. Plus, several of the more advanced ProcessWire fields have multiple fields of their own in their table in phpMyAdmin (in fact I think most/all have more than one). Therefore any other way of storing them in the database simply wouldn't work as well and would presumably be a nightmare to program for.

Templates -> Filters -> Show System Templates : look for "admin" template. Edit and go to -> "URLs" and look for https etc.

Nik figured nice and simple workaround here: https://github.com/apeisa/UserGroups/commit/46161510

ModuleManager updated with ModuleManager , great work Soma.

I think you are looking for: how to create pages, fields and templates using the api. See this topic and this topic with great examples.

I'm new to PW as well, but here goes.... pages This is how I understand it at the moment. The biggest conceptual shift is moving away from the idea that pages are web pages. In PW they are more than that. Pages hold data, so think of pages as more like records in a database. Exactly what data the page has depends on the template the page is using. When you create a new page, the first thing you do is choose a template for the page. templates. (1) Templates keeps track of what data items will be stored with each page eg name, position, phone etc. Each template uses one or more fields, and you decide which fields when you create the template. (These fields can be changed later on, if you wish, but obviously deleting a field will also lose the data associated with that field ). The data is collected when you fill in a form on the admin panel for each staff member, or if you already have a lot of data you can import the data as a csv file using the Import Pages from CSV module, You can have as many templates as you like, and fields can be re-used in multiple templates. (2) the template usually has a php file of the same name in site/templates that manages how the data is displayed. The template php file is where the code goes to produce a simple vanilla display of data, or can get as fancy as you like with tables, tabs, and whatever collection of whistles and bells you like. Each template has access to the $page variable that comes with PW, which can be used to refer to each item of data (ie the fields in the template) on your page, using syntax $page->myvariable to refer to the data in the field. eg If the page had a field first_name, then echo $page_>first_name would print the first name of the person associated with the page. Ryan explains it really well at http://processwire.com/talk/topic/43-template-tutorial/ (3) templates are created from admin>setup>templates>new template. This is where the fields are connected to the template (and to pages using the template). The php file manages the display of the page. It doesn't seem to matter whether you create the php file and import it into templates first, of whether you create a template first without a matching file and ad the file later. To display a page for Fred Nurk, you would have a page using a template with fields for name, phone and whatever else you want to record, and a template php file, with the same name as the template. If your template was called staff, you would also have a file staff.php, in site/templates. If the page for Fred was under a subdirectory called employees, and the title field was used for his name, then the page could be viewed at yoursite/employees/fred-nurk/ fields fields are containers for information. Fields need to exist before they can be added to a template. Fields are created from admin>setup>fields.new field. Each template has a mandatory title field, which is used to when a page is displayed in the pages directory tree. It's also usually used to build the url address that will be used to view the page. Getting information in a page from other pages You can get information into a currently displayed page from another PW page, by using the $pages variable and any selector that seems appropriate. There a number of different selectors that let you locate a particular page or group of pages by a wide range of criteria. The API section on Selectors is a must read and reread.(It's a lengthy page full of essential information and I found it took a while to take it all in - it might be worth printing it out ) The selectors take all the pain out of querying the database .For example, selectors might be used to set up a loop through each of the staff member pages (remember pages are like database records) and generate a list of phone numbers on one page. If you're keeping things like skills on separate pages, then you can use a selector to get information about the skill, and add that to your page on Fred Nurk. In your template php file you would use a selector to locate a page or group of pages, eg $myfoundpage=$pages->get(some selection criteria) or $myPagesArray = $pages->find (some selection criteria), and then you have access to all the fields associated with $myfoundpage through its template. If the template for $myfoundpage has a field for pet_name, then $myfoundpage->pet_name will give you the pet's name. It you want to get really fancy, you can display entire multiple pages inside one master page, using the render method of a page (it comes with that $page that is built into eachPW page.) echo $pageA->render(); echo $pageB->render; echo $pageC->render; would display the contents of all three PW pages on the one browser page. Or you might set up a master/child type of page, where the contents of the bottom part of the page are changed through an ajax call depending on what actions are taken at the top of the page. You'll probably get the idea pretty quickly by getting in and having a go. I'd suggest using a really simple template and going through Ryan's mini tutorial on templates at the end of this post The tutorials section of the forum is a pretty good place to start as well. There's also the wiki

This tiny module is intended as a helper for Ryan's Hanna Code module by providing a way to select existing Hanna Code tags within the editor. This is something I felt our clients needed in order to start properly using Hanna Code tags. See attached screenshot for details -- there's really not that much to it at the moment. Each editor requires it's own plugin and currently I've only cooked one up for CKEditor, where the plugin presents itself as a context menu item (visible on right click). I'm planning to expand the feature set of that one slightly and then probably convert the CKEditor plugin to TinyMCE, but that's just about it. Ideas are welcome, though. Some of the code is pretty much duplicated from Ryan's original module. I hope he doesn't mind -- though for the record I've also tried to make it very clear in the source what part that is and where it's from.. GitHub: https://github.com/teppokoivula/HannaCodeHelper Modules directory: http://modules.processwire.com/modules/hanna-code-helper/

Modules Manager for ProcessWire2.+ Module Manager enables you to browse the modules directory on modules.processwire.com, download, install or update them. Requires the JqueryDataTables module to be installed before you can install Modules Manager. "allow_url_fopen" to be enabled in your php.ini. "openssl" PHP extension needs to be installed on your server. PHP to have read/write access to the /site/modules/ directory For further informations contact the readme seen on modules directory or github. Modules Directory: http://modules.processwire.com/modules/modules-manager/ Github Project: https://github.com/s.../ModulesManager

I've been getting this too with Chrome 32 and I think maybe even on 31 - thought I was going crazy

And what is your rendertime... ?? Just so you know a loading time of the html of 200-300ms is pretty fast and standard.

updated to new version of ModuleManager (v 210). Looks very nice! 3 more strings to check: line 499: $status = $this->_('found:') . ' ' . $local_version; line 508: $status = '<span class="ui-state-installed">' .$this->_('installed:') . ' ' . $local_version . '</span><br/>'; line 514: $status = '<span class="ui-state-installed">' .$this->_('installed:') . ' ' . $local_version . '</span><br/>'; The other strings (Search, Show.. entries, Pagination) are from JqueryDataTables? EDIT: one more string in ModulesManagerNotification.module line 155: $field->label = __('Activate Module');

I'm getting wait times of around 1 second before a new page starts to load and around 500 milliseconds on a reload from the UK. Certainly looks like geography is against you! Getting 304 responses on cached elements now, though.

You may want to consider file an issue on github, as that is reather seen by Ryan and easier to manage: https://github.com/ryancramerdesign/ProcessWire/issues?direction=desc&sort=created&state=open

You're welcome. I always use Google to search the forum, i.e. site:processwire.com adding fields through api

Soma: edited my previous post. Didn't see couple of latest posts until after writing that (and also misread some points), so you can simply forget most of that now.. By the way, Modules Manager Notification looks awesome!

Problems solved, post removed

I actually caught that tweet on twitter yesterday when I was trying to figure out (again) how Twitter works and thought I would search for #Processwire ! Anyways just cast my vote over at Bitnami ( # 462 ) and a tweet as well.... Cheers guys!

I should point out that when I looked at your page it loaded pretty quickly, to be honest.

You could also debug the render time of your page with at the very beginning of your template code: $renderTime = Debug::timer(); and at the end of all when everything is output. echo "rendertime: " . Debug::timer($renderTime); And see what you got.

Yeah that's easy for them to blame your CMS Well you can try and for example save your homepage html to a static file, and upload that to your server and load it and see. (this would be same like using ProCache) I think we can't rule out ProcessWire, but most likely it's not but rather the server being busy with other things or some database connection lagging etc.

Your server response time has nothing to do with ProcessWire perse. This could have many reasons. Since I get response times from 300ms to 3000ms, it looks like your Server sometimes is busy. This could be database or other general server process running. You should ask this question to your hosting support. Template cache only works for not logged in users, as it shows on the template cache option settings.

I notice that you have JQuery called in the head of your page - the same with main.js. That means that the page is having to load the JQuery library in full before it can even get going with the rest of your page Moving those to the end of the page would speed things up a bit.

I just loaded it and it was much quicker than that (see attached). Is it possible you have a sporadic network slowdown at your end? If you really want to speed things up further though, you should perhaps consider the ProCache Module: http://modules.processwire.com/modules/pro-cache/

If I understand what you are looking for, the simplest way I can think of to achieve this would be to turn on the tags field for the images field and then enter "gallery" in the tags for the images that you want displayed in the slideshow. You could order by adjusting the order of the images in the field the normal way, or if you want a different order, you could have a second tag with the order number. Of course whether this is a good solution or not might depend on whether you are setting this up once, or your clients will be doing this regularly. So maybe not a great solution Personally I think it might be easier to have two separate image fields, one for the slideshow images, and one for any other images that need to be inserted in the body RTE.

With PW that's almost always the case

Oh now this looks super-useful: https://github.com/ryancramerdesign/ProcessWire/commit/e5847d667aa200d050815acf73abaeeb30c96493

I'll check with Pete on that one, as I'm not sure we have permission to send mass mailings to forum members. But we do have a good size email list of people that have requested email updates from us, so I could send to that. We still need to promote the contest on our Facebook group as well. I think it might be a matter of timing. As some others have mentioned, these contests tend to get most of their votes at the end, and that might be when we need to make these requests from the community. On one hand I'm a little afraid about us investing too many resources or asking much of people for this, as I recognize this type of voting system can be controlled by motivated individuals with a farm of proxy servers or by using existing web traffic for blind submissions (opensourcecms.com is a good example of what happens). But I also don't yet see any evidence of that going on here, and with the community already rallying behind this one, I am going to do everything I can to support it too. I am hopeful that we can win this one and get PW (hopefully 2.4!) into Bitnami.

http://processwire.com/talk/topic/3426-search-not-returning-3-letter-words/ http://processwire.com/talk/topic/2342-selector-issue-and-differences/ http://processwire.com/api/selectors/

Not especially related to programming, but I just learned of Finnish band Ultra Bra, and considering I speak no Finnish whatsoever and understand not one word of their lyrics, they sound wonderful. I'm just a few years late... (The only other band I really enjoy even though I don't speak the language is Runrig, who sing in Gaelic.)

http://thestationhotel.com.au/ ... for the wonderfully talented designer: http://www.jacinabox.com.au/ (ProcessWire site #32) Cheers Marty

Maybe this can help http://modules.processwire.com/modules/blog-profile/ https://github.com/jsanglier/Pw-News or this http://pivotx.net/ http://www.onlyfreescripts.com/script.php?ScriptID=613