CaelanStewart

Downtime is simple not acceptable, the site is used by executives of the international corporation this site was made for. There shouldn't be many more big updates like this, but I would just like the next iteration process to be easier. Read reply to quote above. And to answer the DB question, we copied the live DB as we cannot work on the live site and risk causing downtime, the mobile app is tied to the site, and the changes are substantial, so the app is due an update too. Well, user's are the most important thing here. I will have a look at that and see if I can't modify it. Will let you know if I attempt it and get somewhere.

Hi, To start off, I'm not talking about upgrading from ProcessWire 2.5 to 2.6 or whatever, I'm talking about a dev/staging/production cycle system. That's all well and good, and works with most of our sites, but one database design aspect of ProcessWire is incompatible with this process. Each user is a page, therefore users do not have a dedicated table in the database that belong to users only. The way I normally see web software designed is that users are "special" and have their own table to be stored in, so when it comes to the time where we put new site features live, we just drop the users table on the local DB and then export the users table on the live DB and import to the local DB. This is because we do not want to disable registrations on the live site as we perform upgrades to the site. I know I could iterate through the users on the live DB, put them all in an asssoc array and then save that array to a file with serialize or json_encode or something along those lines and save user profile photos with a file name corresponding to the user's page ID (and other user created pages), and then run a reverse script on the local DB to add those users back in. Would this work with ProcessWire, or is there more to take into consideration, like references to users in different pages that existed before the upgrade process? We built a site for a large company, each staff member has an account. Each user has profile photos, and each user can submit suggestions for news articles that are saved with PW, those are the existing references I speak of. There is a blog, with several different templates for different types of article, I.E. downloads, events, competitions which all have different types of info (it does not use the PW blog plugin BTW, we looked at it, but it was not suitable). Its essentially an online intranet, so to speak. There is an accompanying mobile app which interfaces with PW through an API I wrote We're not talking about a small user base, there are 250 users on here and it is growing as more and more staff register. There is a custom registration system which adds users in the same was as expected, so user's in the context of this site are no different to any other PW site. What we are going to do in a worst case scenario is put the live site offline for a couple of hours while we download the live DB, repeat all of the changes I made to fields, templates and what not (I logged every changed I made to fields, templates and pages as we foresaw this issue). The version of ProcessWire we have is 2.5.3. I must also say, ProcessWire is dealing with the usage quite well, the site is still relatively quick to load. Thank you in advance for your time, it is greatly appreciated.

Hi All, I'm working on version 2 of http://extraordinaryfb.com/ for our client, I've posted a thread of some trouble I had before, but this time it's different. I'm attempting to add a new page through the back-end CMS, it has a parent with the template "blog-subcategory" (which has no fields other than "Title") and the "blog-subcategory" page has a parent of "blog-category" (which has an image field and the default title field), and the parent of that page is a custom template that lists out the categories and shows three news articles as a preview with a button to see more in that category. Here is a screenshot of the page structure: The issue is, when I create a news article in any of the sub-categories (those are "Regional", "EMEA", "Mission", "Vision", "Logo" etc.), I enter a title, chose the correct template and click on save. The edit page loads and I am met with a huge backtrace log, it looks like something internal, but I'm not sure. Here is a screenshot: Here is a pastebin with the output saved (couldn't upload a .txt file on here for whatever reason): http://pastebin.com/fKhnYeLF I have ProcessWIre version 2.5.3, the core is unmodified barring a css file to change colours in the default admin theme.

Hi all, not sure what caused this, but it's stopped happening now. Thanks.

Hi, I'm in the process of developing a site for a client, however, I'm having some issues with ProcessWire's image resizing tools. I've never experienced this before, and I have used ProcessWire extensively over the last few months. Essentially, ProcessWire generates blank JPEGs and sometimes doesn't even resize it. When ProcessWire generates a blank JPEG (which shows up as being invalid), ProcessWire then thinks it has resized the image, and tries to display a broken JPEG. When ProcessWire doesn't actually resize the image, the outputted file is named ≈ "[file name here].768x0.jpg", which from what I can gather means: $image->width(768); Now, the file it saves is perfectly valid and opens up fine, but it's basically the original image, not even resized... Really not sure how to fix this. There are zero errors in the PHP/Apache error logs relating to this. The page loads fine, the memory limit is high, the version of PHP is what comes with MAMP by default, and is working well on other projects on the same computer. If you need any more details, let me know. Thanks in advance.

I certainly shall do. It is not an issue that is causing us bother, it only took me 5 minutes to fix by upgrading the version of CKEditor that comes pre-packed with ProcessWire. The issue is with CKEditor and Safari. Safari uses a version of webkit that introduced a serious bug in the use query selectors (still not fixed either). So CKEditor introduced a fix so that CKEditor would function on Safari. I reference the posts on this CKEditor support ticket: http://dev.ckeditor.com/ticket/12423

Yes, the CMS will be used by clients. Even when entering text, and then making a quick edit, you can't. As soon as you enter a new line, it messes stuff up. CKEditor (≤ 4.4.4) is unusable on Safari 7.1+. There is no reason I can see that it shouldn't be upgraded. Would that not be a naive decision to leave this unfixed? Especially since this is an easy fix, and it causes the editor to be unusable? This problem was even more of an issue because we installed the ProcessWire blog module, which used the version of CKEditor pre-packed with ProcessWire. You couldn't edit text, or write new text at all, unless you switched browser. But we can't say to the client, you can't use Safari because the editor doesn't work on that. They won't have it. The client's knowledge is limited, and the client just wants to edit the way he/she normally edits stuff. No faff. Obviously I can just do what I've already done each time we use ProcessWire, but surely it shouldn't be up to the user to fix bugs just so they can use ProcessWire?

Hi All, On Safari 7.1+, the CKEditor version shipped with ProcessWire is so buggy it's unusable. For instance, if I type a line of text and press enter, it moves the caret to the start of the line. The expected behaviour would be to create a new paragraph and move the caret into it. The version of CKEditor shipped with ProcessWire is 4.4.3, the issue was fixed in 4.4.5. See changelog entry for 4.4.5: Fixed Issues: * [#12423](http://dev.ckeditor.com/ticket/12423): [Safari7.1+] Fixed: *Enter* key moved cursor to a strange position. I saved a backup, and then overwrote the original 4.4.3 files with the files from 4.4.5 barring some config files with no issue. Anything above that and the instance would not be created. The question is, is ProcessWire going to be upgrading this in their next version? I'd be silly not to. FYI, The latest CKEditor version is 4.4.7.

Hi All, this problem appears to have resolved itself. I'm still not entirely sure what was happening, but whatever it was, it's now functioning as normal.

Hi, I just tested it in debug mode, no difference. Another weird thing I just noticed is when I open up the accordion for /stories/ to reveal child pages (but staying on the same page, the page tree) and then reloading the page, I find I'm logged out. But if I don't open up the /stories/ accordion, and reload, I'm not logged out.

Hmm, I will give those a try. The admin theme isn't really modified, it's just an extra CSS file that overrides the colours on the default theme. We were in a rush to get it out at that point, however. It doesn't affect all users, no. Only some, but the ones affected have been tested on the computer, same network and same browser (tried in Chrome, FF and Safari), and they continue to be affected. But with a non-affected account, on the same machine, there's no problem. The affected and non-affects users have the same uaergroups, in the same order, same email extensions. Weird.

Hi, Thanks for your reply. There is nothing in the errors.txt file from today apart from a login throttle error, because one of my colleagues had forgotten the password to his account and tried too many times. There are no special fields, just title (text), CKEditor and Image upload fields. There are no third party field types on the affected page. And this problem is only affecting some users. A colleagues account has the same permissions, in the same order, and the same email extension as me and he can view the page fine. I created another account, different from the one that created the page, and it still logs the user out.

Hi, I'm having an issue when trying to edit a page through the ProcessWire CMS. When I click on the Edit button, the page loads fine. But, if I then navigate to another page (say, the modules tab) I am logged out. This only happens on a few pages, such as /stories/ and its children. Every other page on the site is absolutely fine and I can edit without being logged out. The weirder thing is when I view this page on the front-end, I am also logged out. It just seems that the simple act of getting a page from the DB causes me to log out, and I can't see the connection. This is causing us some problems since this website is for Hilton, and with 88 people currently registered on the site (and many more to come), we're getting a lot of phone calls. I'm not sure how this can be anything we have done, since we have not modified the Admin Panel or the Core code whatsoever, and that simply going to edit one of the affected pages in the admin panel logs us out. And I repeat, every other page is fine. The website is here: https://extraordinaryfb.com/ Unfortunately, it's a private site, and requires registration with a Hilton associated email address, so I am not a liberty to create an account for somebody to view the site themselves. If anybody can tell us what might be happening, that'd be great. Many thanks in advance. And on a side note, I could not register with my normal company email address since your forum tells me it's an invalid email address. It's a @progress.digital email address, and it is perfectly valid. Only allowing .com/.co.uk and other common TLDs does not conform with email standards. Though I must say, your ProcessWire system is very impressive and we have found it great to work with. Extremely extendable.