benjaminE

PHP version is 5.6 on both The chmod on the wire/modules/ directory is rwxrwsr-x (775), as are all the other directories and files within it (that I looked at).

I've just updated a site from version 2.7.1 to 2.7.2. This worked fine locally, but when I repeated the process on the staging site, I get a list of errors when I log in to the admin control panel. They're all begin with: Modules: Configurable module check failed for FieldtypePage, retrying... I've attached a screenshot of the full list. The site/assets/logs/modules.txt file shows similar warnings. But the site seems to work fine otherwise. Does anyone know what might be going on here and how it could be resolved? Many thanks!

I have a repeater field which contains a textarea field powered by the CKEditor. It works fine under normal circumstances. However, if I change the order of any of the repeater blocks, any text that has been entered into the text area disappears and the text editing area of the CKEditor becomes unresponsive. If I click on one of the buttons of the editor, it works but I get a JS error gets logged in the console which reads: Uncaught TypeError: Cannot read property 'getSelection' of undefined ckeditor.js:386 This is happening in the latest versions of Chrome, Safari, and Firefox and I'm running PW version 2.5.3 Any thoughts on how to resolve this would be super helpful! Many thanks, ben

Awesome, thanks so much for all the help. I've have a look through them all properly and see which one is best. b

Is there any way to disable a user from being able to edit the Name field - that is the field that determines that page's URL? I've hidden the title field, so that can't be edited. I know you disable editing of a page, which would solve this. However, disabling a role from editing a page stop that role from being able to sort its children (see here) and I do want to keep that behavior. Any advice would be kindly appreciated! b

Many thanks for your help horst. If I understand correctly, the first method you mention doesn't allow custom ordering of pages. But the second solution, with the module, does....

Is there a way to have new children appear at the top of the list of children when they're first created (rather than at the bottom) whilst also allowing the user to do custom ordering? I seem to remember seeing this option somewhere but I can't find it. Perhaps I'm misremembering! Many thanks in advance!

Ah yes! Thanks diogo.

Hi Craig, Thanks for your reply and very helpful clarification. And it's great to hear you've found a fix for the problem. However, I thought I was using the latest version of ProcessWire... Is the development version different from "the latest stable" version that's on the GitHub page? If so, do you know where I might find it? Many thanks, ben

I've recently had to install a couple of processwire sites on a cloud hosting service (TSO Host) and have had the same issue arise on both occasions. What happens is that when you try and access any page of the site, an error message - "Unable to complete this request due to an error. Error has been logged" - is displayed. Inspecting the log revealed this particular error: 2013-12-03 05:23:34 ? http://rebeccacharlton.com.gridhosted.co.uk/?/ Error: session_start() [function.session-start]: Failed to initialize storage module: memcache (path: ) (line 104 of /var/sites/r/rebeccacharlton.com/public_html/wire/core/Session.php) A simple fix I found on these forums was to comment out line 155 on the root index.php file: ini_set("session.save_path", rtrim($config->paths->sessions, '/')); But I was wondering whether there might be a more thorough fix than this... I think the problem stems from the fact that on cloud hosting, the root isn't the simple root because you're on a shared server with many other sites. One attempt to solve the problem was to find the true root using: echo $_SERVER['DOCUMENT_ROOT']; and then replacing the "/" on line 155 with the result but this caused the same problem as before. Only commenting out the line entirely worked as a solution but this feels somewhat like a compromise. Any help to resolve the issue would be much appreciated! Many thanks in advance, ben

Thanks for the clarification arjen. Soma: here's the error log I think: 2013-09-18 11:48:42 ? http://www.shootcuba.com.gridhosted.co.uk/?/ Error: session_start() [function.session-start]: Failed to initialize storage module: memcache (path: /var/sites/s/shootcuba.com/public_html/site/assets/sessions) (line 104 of /var/sites/s/shootcuba.com/public_html/wire/core/Session.php)

Hi Soma, thanks for getting back. Unfortunately the site is being hosted on a cloud server and the error logs are not really accessible...

I just realised it might be relevant to mention that I'd installed the ModuleManager module and that there was a file in the cache folder called ModuleManager.cache Might it be that this is necessary? Previously (and when the ModuleManager hasn't been installed) I've emptied the cache with no problem...

Hello, I was having some trouble installing modules (they weren't showing up in the module manager) and so I deleted the contents of the folder site > assets > cache in the hope of fixing this problem. However, having done this any page I try to navigate to on the site (including the root /index.php) throws up a 500 Internal Sever Error. Does anyone have any idea about what might have gone wrong here? It's slightly worrying... Many thanks in advance for any help. b

Thanks for all your responses and apologies for not being super clear. An example would be useful, agreed. So here goes... Let's say I want to create a group of fields which would compromise an article - headline, body, image - and I want to be able to insert this article "chunk" into any given template. A repeater would do the job here, except in this instance I don't want the user to be able to add more than one article (which is what a repeater does best). A repeater is so close to doing exactly what I want, I just wondered whether there was a way to limit the iterations to 1 (like you can with an image field). This would basically solve the problem. I believe adamsprujit has understood what I want and what Ryan is building does sound good, but repeaters are already so close! Pete: the reasons I want to do this with a repeater-like field rather than simply adding the fields one-by-one to templates are: (1) As adamsprujit says: it makes outputting in the template neat, (2) It makes adding the fields to the template quicker, and, (3) It means you don't have to create lots of fields... Say you already have a headline field - essentially a basic text field - and you're already using it in a template, you can re-use it in the same template if it's in a repeater. You don't have to go and make another field - eg, article_headline - to use for the article. I hope that clarifies things. Any thoughts?!