-
Posts
6,798 -
Joined
-
Last visited
-
Days Won
158
Everything posted by Soma
-
This has been subject to some threads. If I search the forum with your thread title I can find some solutions.
-
Maybe you can give more information where this error happens? I just installed and tested it on a 2.6.18 and works fine. Note: BTW you shouldn't install a module with the folder name you get from github: somatonic-ColorPicker-3198273192 .... It's always best to install through ModulesManager or through core Modules New with Classname. "FieldtypeColorPicker"
-
What I would try is install a fresh PW with intermediate profile and edit images, and see if it happens. If not, it may some problems of you're install, third-party module or your own code somewhere. 99% of the cases when such things happend it was a fault of myself or another module and not PW. I've never experienced image saving problems, unless I made my own image field. I remember someone having same problems, so a search turns up: https://processwire.com/talk/topic/3363-image-field-description-not-saving/ Coincidence that there same issue and no solution with a user Ovi?
-
Session Login Throttle doesn't prevent multiple logins with the same user. It's to prevent dictionary attacks, so when someone trying to login 3 times with same username but wrong password.
-
Only you have to keep in mind that it doesn't scale if you do this for more and more pages. Also note that if only counting a $pages->count(selector) is more efficient. Instead of $pages->find()->count What I do on a shop category tree, is calculate it every time a product is saved and write the count to a integer field on the category pages. So it's like cached. You could also use markup cache to cache the output and only let rebuild it when a product is changed.
-
I'm having problem with this module not using translations in template __("Text"). It's always default language for those strings. Ah sorry, I forgot that the pages2pdf template aren't translated yet
-
Page selector getting users with specific role
Soma replied to Whistletoe's topic in Getting Started
No not *. If as custom code for a page select you need to use role id. -
I see, I'll maybe have a look into but will maybe take some time. It's always a lot of work update a module with readme etc, but will put on my list. For now I think a better approach would then be this to replace the UL wrapper class, "MarkupSocialShareButtons", with your own class or extend it: $content .= str_replace("MarkupSocialShareButtons cf", "myClasses", $modules->MarkupSocialShareButtons->render());
-
Outer wrapper? There's none, just an UL So what I do if needed is like: echo "<div class='wrapper'>"; echo $modules->MarkupSocialShareButtons->render(); echo "</div>";
-
I found there's some issues with pages changing values that are used on rules for a dynamic role. It's when I have a filter viewable that says: "on the parent of this page the value on a page select must match, then the user can view the page", as soon as I start change value on that parent page field, subpages won't get updated to reflect this. But they are rebuilt when I change and save the dynamic role. I guess that's by design that it doesn't check for children/parent relations. Which is limiting to how I was trying to use dynamic roles.
-
To my understanding, view access to admin isn't handled by the admin template. It's just that it has no guest view access but a redirect to the processwire login. Once you're logged in, certain other processes are handling the "view" access of the admin, like ProcessHome module has a permission "page-edit" set.
-
Yes, you have a custom login url and no edit rights even for editors. It seems in my test, even if you give them "view" access on the admin template they still can't see the admin. So all little strange. Once you give them "page-edit" permission on the role he has again access to admin. Sorry to hijack this thread, but we were confused as you said to un-ckeck all roles, which in fact are already un-checked by default on the admin template.
-
I think what you describe is already by default, but you define a custom login url and not the processwire backend one. But once logged in they still can access the admin, just have a continue link if they have no edit rights. Thing is that Nukro uses Fredi to edit pages and that requires them to have edit rights set, but they should have no access to processwire backend. So the hook and redirect on admin pages except pages with "FrediProcess" is all needed.
-
I can't see this. I have roles that have no edit permission access. Still on the admin template none of the roles have "view" access checked... Like "test" has only view access...
-
But how do you uncheck all roles, cause they're all already unchecked by default on the admin template?
-
I wonder how this would work, as the admin template already has all roles "view" unchecked, and the login page is the processwire/login. Since when guest user accesses /processwire/ he gets redirected to the login. Once logged in as an editor, as long as he has has at least some "edit" access to any pages template he gains also access to the admin, else he get's a link to "continue".
-
You seem to have a $page->template = 'something' in your template.
-
Cache directory is used by processwire and is not a problem of this module. It should be there already. It will give you errors with every module you install.
-
There's a tutorial board here in the forums where you would post such examples. I don't think it helps much in here.
-
No it's not possible, it iterates the tree structure as is. "parent -> childrens -> childrens". You can only set the top root items per a PageArray. Form there these are iterated down the tree. The selector only is used to filter the children of the current nodes.
-
A new project, we are working on at updateAG, is now online (at least first step, online "reservation" process isn't yet) http://www.walder.ch The data for the shoes are imported from their system va CSV. They then can edit and publish and categorize them as they wish. Soon there will come a reservation process, that's only half implemented yet. It's an ongoing process in all parts and will get reworked or extended by time. They were using Typo3 before and were positively surprized and happy with ProcessWire and think it's all a lot simpler. They can edit all their content only with a rough 15 min crash course "showing" them ProcessWire. Design and concept is from another partner firm, who also executes the print campaigns for the client. Maybe something special to mention: is that we fighted a lot with their product fotos. The plan was to use transparent png's and then so be able to color the background. This lead to a lot of problems with png's and GDlib in general. Plus they delivered the fotos as optimized png's 8bit... etc. Very long story short. With the excellent PIA (PageImageManipulator by horst) and after lot of researching and testing I was finally able to "color a canvas", smash the png on it and have a jpg coming out on the other end! This way, we solved a lot of problems with a simple command and have regained back a lot of flexiblity, lesser artifacts and 10times lesser file sizes at the end.
- 3 replies
-
- 13
-
@Pete Minutes? Last time I checked, it was like not even a minute