szabesz

We already have those, haven't we? How do they help in prioritizing issues? Poll like features attached to issues with some overall statistics could help to see the big picture. Skimming through fragmented bits of info makes things harder that they should be.

I 100% agree that no one needs endless discussions about issues to be solved, what we need is priority and the way to indicate importance. Using the right tool could probably solve this issue.

@Sérgio Jardim Good to here that, thanks for the info. I read that blog post some time ago but forgotten about IftRunner.

Hi @Sérgio Jardim, Does it still work without issues on PW 3.x? I'm not a fan of modules not maintained anymore but this one sounds really interesting. I wish @ryan at least added namespace support and assured us that it will work with future ProcessWire versions as well. IftRunner is not even in the Module Directory.

Thank you! I've just updated the module and keep an eye on what is going to happen onwards.

I do not want to grumble at all, and I hope my positive criticism will not be misunderstood but I would like to point out that ProcessWire's development road is a bit ad hoc these days. Do not get me wrong, I like it when Ryan needs some features and surprises us with stuffing them into the core, but this method of pushing the system further is still missing a crucial step: discussing the features to be implemented/refactored by the developer community. Also, we have a long list of feature requests but no one knows how and when they will make their way into the system if ever. They just seem to be forgotten. Only one example: Changelog support with 890 views and 11 likes possibly hits the 30% threshold set by Ryan but it is still waiting to be picked up. And there are many others as well, also at Github.

Well, something fishy is still going on because both Vienna and Shrook have just reported log entries from yesterday, while I have already had lots of entries after that one too. I will further investigate this when I have the time but now I have asap work to do.

I am sorry for the false alarm, it was my mistake not to investigate what is actually going on before asking you to fix it. It appears that it is indeed Vienna which gets confused and turns – for example – "Tue, 08 Aug 2017 07:27:17 -0400" into "2017. 07. 27. at 14:23". It is a guess but it seems to me that 07:27 is turned into 07. 27. Either way, I need to pick a different RSS reader even though Vienna works well with other feeds but not this one. I just found Shrook for Mac which seems to be ok <pubdate>

Then let's "merge" them! I do not see why we would need two similar core modules. It takes extra time to maintain two. There is not enough time for PageTable to begin with, for example see just his topic. A simple enhancement for PageTable which might never find its way to the module I do not have the time and expertise to do it properly, that is why I opted for the JS hack, BTW.

Good to hear that! When doing so, we should make PageTable deprecated I think, and some migrating aid would be great too. Oh well, I'm just daydreaming I guess...

Hi Bernhard, I have not tried your module yet but I gathered that it does not support Page Reference and Image fields the way PageTable or Lister do. Am I right? Simply inputting non relational data is not what I normally need. Sure, there are lots of use cases for non relational data input but your module seems to be conceptually different from PageTable. What I'm missing form PageTable is column sorting and Ajax editing. Even ListerPro is rather limited regarding Ajax editing an displaying PageArrays ( = fields of related pages ). One last thing: for important features like this one, I prefer using core/Ryan's modules to anyone else's just because of possible compatibly issues in the future. Do not get me wrong, I do appreciate all the work you are putting into sharing your module(s), however I do not feel comfortable with relying on third party modules which cannot be removed without a lot of effort, should the module get unsupported in the future for some reason.

https://webmasters.googleblog.com/2010/04/to-slash-or-not-to-slash.html quote: You can do a quick check on your site to see if the URLs: http://<your-domain-here>/<some-directory-here>/ (with trailing slash) http://<your-domain-here>/<some-directory-here> (no trailing slash) don’t both return a 200 response code, but that one version redirects to the other. If only one version can be returned (i.e., the other redirects to it), that’s great! This behavior is beneficial because it reduces duplicate content. In the particular case of redirects to trailing slash URLs, our search results will likely show the version of the URL with the 200 response code (most often the trailing slash URL) -- regardless of whether the redirect was a 301 or 302.

Hi, Have you checked these? and: https://www.google.hu/search?q=Exception%3A+SQLSTATE[HY000]+[1044]+Access+denied+for+user+site You pasted white text on white background, btw.

+1 PageTable is in desperate need of a big feature upgrade. However, as it is a byproduct of Avoine's need and neither Ryan nor Avoine seems to be interested in pushing it any further, an organized community effort or better yet the very first "crowdfunding" in ProcessWire history could give it boost. I would be happy to join in the fun Maybe @teppo could help us by including this feature request in an upcoming poll of weekly.pw, just like he did with Import/Export.

Thanks for taking a look at it. To tell the truth, I'm not quite sure what actually happens but in my RSS reader (Vienna) the log entries do not show up in the order of the timestamp column. Maybe a bug in Vienna? I will take a closer look and investigate it more detail and report back.

I could provide a few Forum links which deal with issues similar to yours but @maxf5 is right: if you want to render the Repeater Items on individual pages under their own URL then you are better off either using Page Reference fields with Parent/Child relationship in the Page Tree, or you can also use PageTable. Note that a normal PageTable setup is also very similar to a usual Parent/Child relationship setup, however using PageTable has similar benefits as using Repeaters. Repeaters are normally desirable when you do NOT have to render individual pages for the repeaters, such as: galleries, sliders, product variations and so on.

Hi, Isn't it the trendy "rubber band overscrolling" in effect all these browsers seem to prefer these days? Either way, as it is not ProcessWire related, probably this topic should be moved to "Dev Talk".

Hello @zaib I'm not quite sure what your issue with repeaters is. Can you please be more specific? Here are the docs if that helps: http://processwire.com/api/fieldtypes/repeaters/

Currently I am in a situation when a PageArray does not fit the bill: By the way: I kept talking about "one-to-one" when actually what I need is "one-to-many", meaning I need a Single Image (one) selected by VPS from many. I do not need many-to-many as I deliberately want to simplify things.

If you are OK with a hacky solution, then DOMSubtreeModified might do it. I'm not a JS guru but a few days ago I used it to detect "AJAX update", well, sort of:

This post by Ryan partially answers your questions: Regarding the admin login process, I do not know if it helps you or not but recently I used two hooks to use the admin login for frontend login as well: <?php $site_customers_pid = 'customers' /* Redirects frontend user to /customers */ $wire->addHookAfter('Page::render', 'siteProtectPages', array('priority' => 654)); function siteProtectPages($event) { $current_page = $event->object; if ($current_page->template == 'admin') return; // ignore admin pages including admin login page if ($current_page->path() == "/{$site_customers_pid}/") { wire('session')->removeNotices(); // needed to clear "left over" notifications of the login page } } /* logout hooks for non admin users * see: https://processwire.com/talk/topic/15911-redirect-home-after-logout/#comment-142170 */ $wire->addHookAfter("Session::logoutSuccess", null, "setRedirect"); function setRedirect(HookEvent $event) { if (wire('user')->hasRole('customer')) { wire('session')->redirect("/{$site_customers_pid}/"); } } And "What to do when user attempts to view a page and has no access?" is set to: "/admin/login/". With this setup when the visitor goes to /customers/, they see the standard login form. After logging in, they get access to /customers/. I styled the admin header and login form with CSS and JS to make it more like the site's design. I know that this is somewhat off topic but it might give you and idea or two.

Thanks for sharing! Installed it, works great

Hi @teppo, Bug report: (sometimes?) in the RSS the date shown is the Created date of the Post not the Modified timestamp. I've been able to live with this, however, should you have a minute or two, chould you please fix it? Cheers

Hello @jothanne and welcome to the forums! Are you looking for something like this?

Yep, it is worth spending the time on this stage, I 100% agree! This is the key to get to speed with ProcessWire based development.