Leaderboard

Came across this from contentessentials with an interesting sum up and migration: http://www.contentessentials.com.au/resources/essentially-cms/the-processwire-advantage/ http://www.contentessentials.com.au/resources/essentially-cms/migrating-a-web-application-from-drupal-to-processwire-a-case-study/

Official Announcement: http://blog.getbootstrap.com/2015/08/19/bootstrap-4-alpha/ Hacker News Discussion: https://news.ycombinator.com/item?id=10086651

Sorry for the stream of updates, but you can now embed BCE into the flow of fields within the Content Tab. This makes for even easier access to inline ajax editing of child pages. It probably only makes sense for Lister, Edit, and Export modes. Just pushed this option to the dev branch.

I'm not really sure how this is selecting 1|3 here, but there's certainly a lack in checking for empty strings in the FieldtypeOptions::sanitizeValue() function. To fix this add this right at the start of the function: if($value === ""){ return $this->getBlankValue($page, $field); }

this.look like a repleye to questiones here http://processwire.com/blog/posts/processwire-2.6.13-and-a-preview-of-prodrafts/#Comment11880 allso pw all ready having sweet versionings frm weekly.pw.teppo http://modules.processwire.com/modules/version-control/ i make draftas this like 1.installs processPageclone frm core 2.clicking copy.on page in.tree { page u want.draft of } 4.edit.edit.edit { keep unpublishas } 4.get mom to edit.fix.edit blahblahblah shutup mom 5.ready to publishas ? trash.originalas page 7.rename clones page and clicking publishas edit 8.ok mabe i will.try prodraft

Hi LostKobrakai. Thanks for your answer. Here is a step-by-step guide: 1. Download Processwire 2.6.1 Master from http://processwire.com/download/ 2. Upload PW with site-blank profile to Server 3. Install PW 4. Login to PW-Backen 5. Modules -> Core -> Select Options -> Install 6. Setup -> Fields -> Add New 7. Basics Tab -> Name: test -> Type: Options -> Label: testfield 8. Details Tab -> Select (Single Value) -> Selectable Options: test1 (new Line) test2 (new Line) test3 9. Actions Tab -> Add Field to Template "Home" 10. Save (Add Field after title) 11. Pages Tab -> Home -> edit 12. Choose test1 -> Save 13. Choose "blank" (no Value/Option) -> Save 14. Now I check the Database and there are 2 Entries for the same page_id 15. open home.php with an editor -> write "echo $page->test;" under "include("./basic-page.php");" -> Save and upload it to the server 16. Open the Home Page (Frontend) with browser -> the echo command outputs "1|3" means 1 for the first Entry and 3 for the last entry. If I add an Option (see step 8) e.g. test4 the echo command outputs "1|4" aso. I have not done anything else! Meantime I tested it on two different Servers (My Local Server and EDIS-Provider where some PW-Pages run successfully) and the phenomenon continues to exist. I think (and Ryan confirmed it in the poste further above) that it's unusual -> the echo command should output no value (blank) instead of "1|2" or "1|3" ... Best Regards Robert

MarkupSocialShareButtons This module outputs a list of share links for the following services by default * E-Mail (kinda extra) * Facebook * Twitter * Google+ * LinkedIn * Thumblr * Reddit (off by default) * Pinterest (off by default) Usage examples echo $modules->MarkupSocialShareButtons->render(); This outputs a simple UL list with links <ul class='MarkupSocialShareButtons cf'> <li class='mssb-item mssb-facebook mssb-popup'><a href='url'><i>facebook</i></a></li> etc ... </ul> Config Screen See more details and examples on github or modules directory https://github.com/somatonic/MarkupSocialShareButtons http://mods.pw/8j

Hi, I just wanted to sing a song of praise of how smart actually PW is (designed). From my recent posts here in the forum you may know what I'm currently trying to do in my spare time - I port/migrate a fairly popular handbuilt 16 year old forum over to process wire. Reason is; the forum's users have grown to like the not-like-the forums out there look of the 16 year old originally perl/cgi based thing, which basically is nothing else like a nested list in most views, which then got enhanced whith loads of custom pages, functions, galleries and wutnot. 16yrs worth of procedural php code, created by at least 4 different and differently skilled developers. Bring it on! Whatever the reason, I thought this might be the perfect pet project to get to know PW in and out. And I really have to say: I'm deeply impressed. I have over 15 years experience wiith different CMSses, and I consider myself as fairly skilled in TYPO3 (yes, with that Typoscript riddles), know my way around cutsomizing and theming Wordpress sites since wp2.1 and I messed around with several other popular and not so popular CMSs as a part of my daily work. For like 1.5 years now I use PW as the "motor" of most sites I build. And now, with this "pet project" of mine, I'm really starting to fall in love : Being able to bootstrap the API and creating scripts that I can "fire" via the commandline, directly on the server, connecting to other databases, helped immensly with the task of getting 186000 posts by 5000 users into a processwire install. creating the relations between these posts (which one is the root of a "discussion", what is the "parent" of the current post) was easily done be using "Page" fields and again a script that scraped that info from the old structure and populated the page fields accordingly. I plan to write a detailed how-to once the migration is completed and working, but this could take some time ;-) Now the backend would time out if I wanted to edit one of the post. Caching the templates didn't help, so I thought about what was going on "under the hood" -- and after a little bit of head scratching it occured to me that maybe the 4 "Pages" field each post carried, were to blame, esp. the 2 fields referencing the whole collection of posts: "post_root" and "post_parent" -- each of which could theoretically be one of the other 185999 posts in the database. Since the default option for the visibility of "pages" fields are "select" and "open", PW needs to query the 185999 posts - and that brought down my php script execution limit and/or the allocated memory size of 152MB. Wow. But guess what, and that's where my romance with PW started for real: If you switch the visibility to "closed", or in my case to "closed with ajax on opening" the backend will run fast again. Now the selects will only be populated (with ajax) if I need to change the post_root or post-parent - which should never be necessary in the everyday use of that data. Initially I had imported the 4000 users not with the system's user template, but a custom one. While this worked without a problem, it brought down the lister, which wouldn't respond and time out after like 5 minutes. I still don't know why, but changing those users to the system user template got rid of that problem, and now they are behaving quite well. This is so cool. What started as a late night idea seems now to grow into a real project. With all that importing and moving imported data to pages data, I had like half a million pages in this install, and PW handled this quite nicely. In the meantime I have cleaned up and currently I'm down to about 186000 pages plus 4000 users plus some static pages. This wouldn't have been possible without the option to use the PW API from the outside. Thank you Ryan for this great piece of software. Cheers, Tom

I have used Cyberduck for a lot of time, and well, it does the job. Keeps my bookmarks, easy to use and allows a custom text editor. But I am always looking for tools to make my workflow faster and painless. Do you guy have a recommendation to change to another client? Maybe due to featurewise benefits? For example, the file sync in Transmit looks promising. Forklift also looks promising. Anyone working with these? Note: I have tried sync with Cyberduck, but for some reason, I can't never get it to work correctly, or as I expected, one time I even replaced my whole folder with empty files. (I probably did something wrong myself, I know)

Hi Guys, Here's another website from us. It is some months old, but I was waiting for all the content to be in place before showing. http://davinci-porto.pt/ This is a frames workshop and art gallery in the main art neighbourhood from Porto. the content is in Portuguese, sorry Exceptionally in this site, there was no intervention from Erika, so the design is mine.

That's a better description...Like @tpr has suggested, this would be better managed on the admin side rather than in an include file for at least two reasons: 1. Your images will have a description - no need to type that text in some template file where your client/editors will not be able to change it 2. Dynamism...in case needed in the future. Here are some options: Option 1: Create an image field (e.g. call it content_header). Attach this image to the template used by your parent pages (Whale, Guppie, etc). I am assuming all these parent pages have a single shared template (please note, I am talking about a template here; not a template file). Image fields have a description text area. Use that for your 'brief descriptions'. content_header->description will give you access to those descriptions. More here on image fields. Then on the children pages' template file(s) call on their parents' image field and description...e.g. $page->parent->content_header->description Option 2: Create a dedicated page to hold all the content headers and their descriptions. Let's call it 'Content Headers'. Add one image field to it that accepts multiple images. Add your '25' images named similar to your parent pages, e.g. whale.jpg, guppie.jpg, etc (if practical, or use some other naming format). I can't remember if you can use the API to find an image using its name (i.e. $image->basename). Anyway, you can activate the 'tag' text area of an image field (in the field's settings). In that case, no need to give your images any specific name. Then, give each image a tag that is identical to your parent pages names or titles. You can find each specific image using their tag, i.e., $page->images->getTag('mytag'); Or, in your case you refer to the dedicated page, e.g. $p = $pages->get('name=content-headers'); $chImage = $p->content_header->getTag("$page->parent->name"); If you gave the whale header image a tag called 'whale', then, when viewing Whale's child pages, this image will be retrieved. The advantage here is that you can edit all your content headers in one place. Option 3: If your descriptions are quite long, then, create a dedicated text field(s) and a separate image field using either of the above options Option 4: I think you could also use repeaters or PageTable(?) Haven't tested the above code and I have been away a while, so, there could be other better ways to accomplish what you are after.

I've to say, that I never got warm with Forklift. It tries to hard to be kind of a finder replacement, whereas Transmit just does one thing and that exceptionally well. The synced folder feature is just the best and if you set the local and remote startfolder for the favorites, than it works from the beginning and you just drag&drop files around.

Although it works, seems a bit strange that you are exploding the page's URL string to get (I suppose) the name of the parent page. ProcessWire already has methods and properties to get you all the information you need about a page (similar to my example above). What might be a 'better' way depends really on the answer to the questions: What is the content of headerImage.inc (is it just an image?) Is that content dynamic in itself (i.e. will you be editing headerImage.inc) or static? Otherwise, like I said, there could be a dozen (better ) ways to achieve the desired effect. You could still get away with one or two templates. Depending on the content of headerImage.inc you could have for example a single page with all the header.incs as fields, a single image field that holds multiple images, several pages, etc. Hard to answer without answers to my questions above ...

@mr-fan - thanks for the great feedback, testing, and the PR for language labels. Yep - I think the issue with the Lister view not working when there is an images field selected is a problem with PW dev / Lister I don't quite understand the Normal/Ajax load problem (I am sure I am missing something obvious so will look better later to see if I can figure out why that needs to be an available option when Open is checked. Yep - I was planning on making the Lister EDIT mode configurable to include the modal option, but there is something stopping it from working properly in modal mode - I think it's because Lister is in an iframe, but I will look again and see if I can get it to work - it would be much nicer for times when inline/ajax editing is not enough (or the user doesn't have ListerPro). I am also thinking of making it possible to choose a different parent (or maybe even use a full PW selector) so you can make BCE grab children from somewhere else in the page tree - I think this would only work for Lister, Edit, and Export modes, but could be very cool - kinda like the ability of PageTable to specify a different parent, but even more powerful. I'll hopefully play with this in the next few days and post a new dev version then.

Currently ProcessWire names image variations like this: myimage.[width]x[height].jpg But there are other image sizer config options that affect the image variation - namely upscaling, cropping and quality. If you change any of these config options after you have already generated an image variation at the same dimensions you don't see the result on the frontend, rather you get the old cached version. There is a module that can clear image variations, but the problem could be avoided if the config options were included in the variation filename. Something like: myimage.800x600.u-0.c-north.q-70.jpg

You are a real bad guy....with all this "stream updates" just one tick while testing... https://github.com/adrianbj/BatchChildEditor/pull/4 (changes the labels on the field selection in the right language) The issue with Lister view if there was images is a problem of the actuale PW dev i think? For BCE i tested today very much and the next days german translation follows....while testing i've to say just one thing but i think i'm repeating me: THIS IS A SUPER MEGA GREAT ADDON.... some little testing things: - Setting (Editor,Position, Load...) ->Position = Inline Fieldset, Insert After = title, load the fieldset open = true, ....Open Method is hidden if loading the fieldset collapsed but "Normal" or "Ajax" loading should be selectable while this setting enables the inline editing, too not only the loading? - A "modal option" for lister mode should be a little additional option for the lister edit links, to edit childpages in modal mode... This is really great if your wanna a easy and nice overview page on such root pages for the same kind of content like team, tags and articles or similar....i'll embed it in my current projects since it is much more flexible that a pagetable for this task! And a additional call for others to buy Lister Pro... Best regards mr-fan

No worries...I was just about to post to ask for clarification (i.e. in cases where there are lots of headers to include).... OK, just to get this straight... You have 25 different headers? You do not wish to use 25 different xxxx.inc files What are the differences between the headers? Markup or content (text)? I ask because there are different approaches. This could either be done template file-side or pages-side. E.g. different header content could be stored as pages and rendered as headers. This topic might also be of interest: https://processwire.com/talk/topic/740-a-different-way-of-using-templates-delegate-approach/

Not sure I follow but if your header.inc files are each named similar to the parent pages, e.g. whales.inc for /whales/, goldfish.inc for /goldfish/, then something like the following should work. Add the code to the template file of the child pages (i.e. the template file used by the children of 'whales', 'goldfish', etc.. include ($page->parent->name . ".inc"); Ideally, you also need to deal with what should happen if PHP does not find the specified include file. Welcome to the forums

@Juergen and all multi language friends: In this thread post #88 "kixe" has posted an update to Ryans template with added language alternate-links like recommended by google for multilanguage support. This seems to work fine so far.

Forklift in combination with Sublime Text is pretty unbeatable for simple FTP and text editing. Also, I wouldn't rule out Coda, which is basically a text editor with most of the features of Transmit, all in 1 app..

I've used Transmit since it was released. I usually don't think much about it, which is good. It's always been rock solid. Forklift looks very interesting, I'll give it a look.

Yes, can not agree more with that. Your post summed it up very well. I hope Processwire will never take the road of a washing powder to stay in the picture: "This Month we have added feature xyz and now you are able to do abc like never before" Let's never forget why so many people (e.g. from modx) migrated to Processwire: No typical, no shine, no show or fancy but raw power ! Sometimes I have my doubts if the core of Processwire will stay like this because if you look around in the world, the temptations of becoming part of the status quo, buzz or popularity, is immense. I hope Ryan and his team will never fall for it. The focus should not be the core but marketing Processwire.

i.need two triy forkleft but i like yummy.ftp

Forklift looks great. Thanks for the tip Adrian. @elabx Transmit is good and I can recommend it. I think the version purchased via the Apple App Store has a sync limitation or can only sync via DropBox and not use it's native sync function. Also remember using it the first time and noticing that it prefers drag n drop over uploading a file. If you upload a file the normal way make sure "Linked Folder Navigation" is on so your folders will navigate in sync, local and remote, at the same time. Always found Transmit support very good too.

I utilize Forklift and have enjoyed using it since converting from Windows to the Mac. I have not used any of the other MAC (S)FTP clients.

Forklift is my tool of choice - great FTP client and more importantly for me, a really nice dual pane Finder replacement which I can't live without!

Hello again! Now I made a new/blank installation without "multi language" or any other modules except the "Select Options Field". I didn't make any new fields or templates beside an Option-Field called "testfield". Unfortunately with this new installation I can reproduce this issue too... In the attachment you can find some screenshots from database, PW-backend and frontend-output with <?php echo $page->testfield; ?>. I have already mentioned that this issue appears, when I firstly choose one option and save the page -> then I set it back to blank and save it again. Does anyone have any idea?

Ryan already has the module to edit config in backend since 2.5 in his repository. I'm working on a new multisite version but doubt it will be ready anytime soon.