Neeks

I was able to reproduce POWERFULHORSE's speed issue.

some images hang for 30-40 seconds on an operation after they have been successfully rendered once.  

PHP: 5.4

PW: 2.4

GD: 2.10 compatible

CODE:
 

foreach ( $albumimages as $albumimage ) 
{
//FAST
$imgSrc = $albumimage->size(1000,600,array('upscaling' => true,'cropping' => false,'quality' => 70))->url;
//Fast with some files, but killer slow with others
$imgSrc =$sized->pimLoad('watermarked')->watermarkText("Gail Gelburd", 20, 'SW', 5, 100, null)->pimSave()->url;
//... 
}

The PIM portion of this operation can hang the the page for many seconds, even after successful rendering of page it does not get any faster on subsequent  page loads.  I can Upload the offending images if that offers any clues as to what can be going on.  If I can offer any additional debug info that might give any helpful clues as to what is going on let me know. Thanks for a great module Horst. 

Thanks, sorry about that I just saw "compatability 2.4" under the module page, but after reading this forum post more I realize you do mention I need the latest dev branch. Will make sure to read the whole thread before posting next time. Thanks Teppo. 

When installing module from Module Manager on version 2.4 I get this error on install, and when I try to visit the modules page.

 Error: Class 'WireMail' not found (line 19 of /home/gelburdg/public_html/site/modules/WireMailSwiftMailer/WireMailSwiftMailer.module) 

uploading module manually seeing if it fixes it. 

wonderfully simple! thanks Soma.

Hi Soma,

Thanks for the reply. I wish it was that easy. I need.  $page->methods(), to work as if they belonged to the original page. But have content from "someotherpage". Maybe that is really easy, maybe I just need to save and restore $originalPage->id and $originalPage->name and all the methods will still work. I'm not sure. Reading the API docs it seems like its not something that a lot of people need to do.
 

The why of all this silliness: my company is investigating PW for a large project. i'm wanting to setup a revision system for multiple developers working out of one central process wire install for content that is pulled down into lots of test environments.  Some times we have to push code and content changes that need to go from testing status to live status at the same time. With lots of devs we are trying not to conflict with each other and overwrite each others changes since we have code branches with content changes that can hang out and diverge from live site content for weeks and need to get integrated at some point. So imagine that situation times many devs. We need to be able to test different versions of content without it effecting live content. We are currently faced with several models. A single centralized server that allows for alternate versions of of pages to be pulled into test environments and loaded if they are available, a locking model which gets us away from merging all together, or to push changes from test environments to our central server using a modified migration tool. The migration tool is great, and i'm playing with it, but we are trying all out options and seeing what is combination of options is going to work best for our workflow. 

The centralized server version works like this:

Dev copies the pages they need to complete their tickets to "/branches/", (automated with a little button called "create branch"). It creates a page relationship between the original page and the copy in the "/branches/" part of the tree. This relation makes it easy and fast to test if a page has an alternate version that we need to load on the front end. (if $page->branchPageFeild == $currentBranchCookie GET "alternate page object") Its pretty important that this page replacement can happen as transparently as possible.  It is also important that all the other functions of the original page work as they normally would as to to not break all the original $page->methods().  if i do a $page = $pages->find('/branch/some-other-page'); my $page->children() calls will be broken unless I copy all the the Original page children, $page->parent() calls would be broken for sure. 

Branching is a necessary evil of our current work flow.  (we do use locking as well, and prefer it to having to merge content, but some times you got to branch and merge content...). Once we get this working on a single server I can play with pushing pages back and forth between servers using json. IE "Push Page to Production Server" Button....

Any thoughts on how to make the first part of this work though ($Page =$NewPage AND Keeps original $Page Methods  )?

What is the best way to copy all the field data from one page object to another without overwriting things like ID, and name? or anything else that won't change the original pages contextual methods like. parent(), next(), from working as they would normally, 
 

I want to replace my $page object on-load using with another $page of identical field structure just different content.  

in processwire 2.4 any one seeing ":ignore:"  in their $page->body fields on "preview" (rendered page, when preview button is clicked) rather then seeing the body text?

Thanks, PawelGix.  I stalled on 2.4  PW install. Pages -> Home -> Admin -> Pages -> Pixlr Image Process does exist.

I'll try installing on another 2.4 site on another webhost see if I have more luck. Awesome Idea for a plugin. Look so forward to using it

Update: so I just installed with the module manager on a different PW 2.4 site on a different host, and go the same error.
Commonalities between the two installs: Using Chrome Windows as browser (latest version),  used module manager to install.

Other modules Installed: CK-Editor, Thumbs, colorpicker, batcher.

​Nothing of noteworthiness in the proccesswire logs. I'll try a manual install a little latter and see if that fairs better. 
 

seems like a really cool plugin

will try on another install and install manually see if I have more luck then with the modulesmanager. 

After install with modules manager: 

  Page not found. 
at URL: ...../processwire/page/pixlr-image-process/

Also get this when I click on the pixler express:  
 

The server can not find the requested page:

Jlahijani, thanks for sharing you experience with the system. If you are building a true web app, you don't need the CP, and then your just relent on the API so why not go with a framework for app building. Makes perfect sense to me. 

I have made the mistake of building projects with the wrong tools before. (a learning management system in expression engine), and while it's doable, it's way better to have the right tool for the right job. (processwire would have been a great tool for that project though, had I known about it at the time (almost perfect...no Amazoon S3 files yet)). 

Hi jlahijani,

in your bookmarking demo you mentioned you cashing your rendered HTML in a custom field. Does that mean you are using PW built in tag cashing or you created something different. Would love to hear learn more about the project as well. 

Thanks. 

adrian I can see you put a lot of love into that module. looks really promising. It might be just what i've been looking for. 

I want to get some tips from the community about using process-wire in production environments. 

Workflows for lots of devs and editors, any tips?

I am wondering if any one has used processwire in an APP or site that has lots of editors, and many devs all needing access a site to be able to make changes to nodules, content, codebase, etc. If so, how do you handle it, what is your workflow and how do you keep things sane?

Adapting to existing workflow: any tips?

I am currently working at a company where we have lots of test server environments, and most of our changes are through git. So in our workflow we are pushing changes from test server to test server, getting reviewed, then pushing code to production. many changes are developed concurrently by many developer, and pushed to public server.  I'm wondering if processes wire could adapt to a similar work flow. Being able to export database field changes from one server to another, or page changes from one server to another.

I realize that this would have to be done with care and a some custom modules will have to be written. One thought i had was to be able to export part of the process wire tree from one server to there other, and if there are changes ask, if they should be overwritten.  Not sure if SQL or API would be the best way to go (or a mix). Any one who has experience with exports please let me know what your thoughts are on this, or if its even worth the effort. 

my other thought is to propose an alternative workflow, where databases changes don't move between servers as much as code (which could be possible) but its a cultural shift and I would love to hear what others are doing. 

What are the problem areas with exporting/importing sections of the page tree between servers? will repeaters give issues do to how they are stored in the DB, will that new tables feild move between pages with ease. 

My other thought was to be able to export DB schema changes or field changes.  Again not sure if API or direct DB access would be the best way. Also not sure how friendly pages and fields are about being moved from one server to another, it might be a big can of worms, so I am asking before being the one who gets stuck with the can.

this topic inspired me to think about a very basic change to the existing image setup that would at least make managing images a little easier.  Doesn't address the broader issues that are being talked about would at least make the existing system  a little easier to use when dealing with a lot of images. 
 

main feature is it shortens the list if you have many images with fields. It will probably even let you squeeze an extra field in like "title" if you wanted it.

just an idea...I really like how it works now compared to word-press or expression-engine image management.

@GuruMeditationi
it's worth looking at the source code for the module. it is 410 lines of code. It's pretty bare bare bones as far as forum's go, but the essentials are there to build something awesome if you have the time.  

"Private messages"

You would have to create this feature but, this page makes it seem pretty simple.
 

"Profiles, with the ability to add extra fields etc."
Supported through processwire. All users are pages and can have custom fields. 
 

"An option that allows comments on articles/pages etc to create a new forum topic, so that users can reply in the forum, or on the actual article/page etc."

I'm wondering about the "best" way to do it myself. But certainly looks possible.
 

"Moderation tools, copy, move, close, pin, ban etc."
copy, move,  delete are all possible through the admin interface. Ban, close and pin would require some simple changes to module i think.

Does not look like there is email notification/topic watching support yet either.  

Forgiveness in for any wrong information, I hope some one can correct me as I am still pretty new to all this as well. 

apeisa: was wondering if you can share the any URL's that uses the forum module you created. Would be great to see it in action.  I was also wondering if you think using CKEedit with this module on the front-end would be advisable/possible? 

would using fredi in conjunction with forum allow for this or would that be a giant security blunder? Better to include CKEditor JS on the front end of site?

PW 2.4 : I think its a firewall issue. 

my site was working great and now for some reason when I try to save I get a white screen. no errors in /assets/logs.

I found out that when I save I am triggering this rule on my webhosts firewall.  

PREROUTING 249 47 2424 REDIRECT tcp -- !lo * 68.118.192.112 0.0.0.0/0 multiport dports 80 redir ports 8888

_________________

any one know why process-wire would trip up that rule? 

UPDATE:  My web host was kind enough t fix the issue for making an exception for my site. I just thought it was weird process wire might try to access port 8888 on save. It is possible my web host was not giving me the correct information. 

Hi, just wanted to say that my error: 500's magically fixed themselves. No sure if the  module manager was just having a hard time connecting to the server to get a listing or what. But my modules manager seems to be working flawlessly with no changes on my end. I increased the listing limit, all seems to be working great without a problem. Thanks.

module manager worked great until I upgraded to the latest version after upgrading from pw2.3-2.4 and upgrading to the latest module manager at the same time I kept getting:

"500 Internal Server Error"
 

Note: old module manager worked under 2.4.

I searched though my logs but an not finding anything in the porcessiwre error log or my apache error log.

every once in a while the page does load with the words "processings..." and "loading..." by the module table

when look at my js console it says "502 bad gateway"

90% of the time I just get the error 500 and don't even see the module manager table. 

I have tried setting max redirects from 0-25

and limit from 0-200

------------------------------------

Please let me know if there is anything I can do to provide better debug information. 
 

This module is amazing and just want to give so much thanks for all the hard work that went into it. 

really well done. love all the subtle transitions on the page, and it still runs fast....Your <head> code is so organized...Really awesome work. 

Dave p: thanks for noticing! 

stunning! i'm totally inspired. 

My first process-wire site for a client! Been working on it this week, will add a blog. It was my first 2.4 project. I'm loving 2.4. I put a font awesome icon on everything in the backend! makes me feel good to have icons for some reason. I am hoping I can just save this site as a "template" and use it for future projects as a base. 
 

+ this was my first zerb site.
 

http://www.principlededu.com/

I started this project as a wordpress project using Avada theme. a theme that got like 20,000 downloads or something crazy. It looked ultra flexible. But when it came time for client to edit, and they saw all the short-codes, they said forget it! 

 
(this is an example of an "easy page": the home page had more shortcodes then content)

So I decided to give PW a try. It made for a much cleaner solution. (screen shot of home page) the page got more complex, and the client is editing happily.  

Anyway that is my success story, still working on the the project now, and open to any feedback and tips.

the ability to close all repeater rows by default  + title would make navigation pretty spiffy at a glance.