szabesz

Thanks for the quick reply with clarifications. Tabs could help either with "custom" fields or with "inventory dash table" too, as you could separate them from the main products edit page. Especially for custom fields, tabs based separation would be great and that way you might be able to separate the two worlds of Padloper 2's GUI from PW's inputfield type based GUI.

Thanks for the report on the progress you are making! I have a few observations and questions. I know that at this stage of development it is not top priority and hopefully things can be fine tuned later on, but I would like to mention that excessive usage of whitespace – i.e. uselessly big padding – is against good UX. The more one has to scroll up and down, the more tedious it becomes to work in the admin, especially on laptop screens. I made a quick mockup to show what I mean. I moved the action GUI bits in line with other action like features. I also marked areas where whitespace could be made smaller: My questions: Are you planning to utilize tabs (for example) on the Product page? Variants section is a good candidate to be separated under a tab, for example. Are we going to be able to add "custom" PW fields to products? I already have sites with product catalogues waiting for Padloper 2 to be added in order to implement shop features. However, all custom data should be kept somehow. For example, I use repeaters for simple variations and each repeater – among a few other fields – has an SKU and also an EAN-13 barcode field. Also, a product itself has various other fields, such as Option Select fields and page reference fields with ASM select. In the video, Inventory management seems to apply to the product and not its individual variations. Is that correct? What fieldtype will Padloper 2 use for prices? When supporting currencies, it is quite common that a product can have a price in the 10000.00 - 100000000.00 price range, which is not something PW's FieldtypeFloat can handle (maximum is 9999.99 with FieldtypeFloat). This is why this request is so popular https://github.com/processwire/processwire-requests/issues/126 but unfortunately the is no sign of Ryan adding it to the core ? Thanks in advance and keep up the good work!

What I meant was that we could be allowed to pick one of those listed here: https://validator.github.io/validator/ and not any other out there.

I do not know about that, but it works well with BBC's iPlayer.

BTW, I was not suggesting doing it in the panel, but in the module's settings. Isn't that possible either? Am I misunderstanding something?

I see. Thanks for updating the module!

I would probably need to spend 2 or 3 days on it. I guess it is not comparable to the time-frame Adrian needs to do it.

Is it just me who is upset by not being able to validate "real-time"? Anyway, in Tracy's source code I read: "what about switching to: https://checker.html5.org ?" So I just manually changed it to : $this->validatorUrl = 'https://checker.html5.org/'; Seems to work. @adrian Any chance of adding options to the Settings so that we can provide a working ULR without changing the source code? I am thinking of a text inputbox, so that any working service can be provided, just in case. As far as I can see, currently we have three options: https://validator.github.io/validator/ of which html5.validator.nu/validator.nu does not work at the moment.

Thanks for sharing! That would be a good thing for sure but even better would be to add it to the core ?

+1 over here

Because of this, is it worth also confusing the maintainers of the site? When debugging issues, it is easy to trip over files named in misleading ways.

validator.nu (utilized by Tracy) seems to have been down for more than 16 hours or so. Most "is it down or just me" websites also report that it is down, a few report it is not down. Does anyone have more info on this? I could not google any news regarding this issue.

And that is "ProFields Table" and not "ProFields: Page Table" included in the core, right? I find it confusing that these tables are so similarly named.

Are you sure? I'd love to know how to enable this if possible. All I could find is this post: https://processwire.com/blog/posts/fieldtype-pagination/ Quote: However, because it's being added as a core capability, it's likely we'll be supporting the same in other Fieldtypes like Repeater, Repeater Matrix, PageTable, Multiplier, Files and Images. So this "likely we'll be supporting" statement never seemed to become reality.

FYI: https://uppy.io/blog/ "Today, after 3 years of development, we are launching version 1.0 of Uppy, our file uploader for web browsers." "Saves battery and data plan by letting users pick files from Webcam, Dropbox, Google Drive and Instagram, while letting servers do the heavy lifting via Companion"

I think you should go ahead and file it as a bug report because superusers shoud be able to trash/delete.

Thanks for the tips! Note that @adrian's Tracy Debugger has similar options – in the case that one is installed too –, just look for: Indicator type and Custom Indicator CSS in settings.

I think it will required a complete rewrite, based on some JS "framework" magic... Sure. While adding UIkit 3 to the mix was possible, it just added another layer of complexity. The current admin is a patchwork, although a good one, but there is room for improvement as always I think. Ryan likes proven tech, so I wish he took a closer look at JsViews by Boris Moore: https://www.jsviews.com/#samples/editable/submit 6+ years of constant development without breaking changes and reinventing the wheel, in this sense similar to ProcessWire's path, so I started using it too. It took me a while to stumble upon it by accident.

More on this: https://www.i-programmer.info/news/81-web-general/12700-google-attempts-to-fix-amp-makes-it-worse.html Quote: "AMP is a walled garden under construction." Sadly, macOS too: https://www.i-programmer.info/news/201-ios/12681-is-the-walled-garden-about-to-close-around-macos.html Quote: "Beginning in macOS 10.14.5, all new or updated kernel extensions and all software from developers new to distributing with Developer ID must be notarized in order to run. In a future version of macOS, notarization will be required by default for all software. (A notarized app is a macOS app that was uploaded to Apple for processing before it was distributed.)"

Quote: An open source version of Visual Studio Code that doesn't pass telemetry data back to Microsoft has been released. VSCodium aims to offer a more private development experience to Visual Studio developers. https://www.i-programmer.info/news/90-tools/12704-open-source-visual-studio-code-without-trackers-launched.html On my mac vortex.data.microsoft.com is contacted once a minute... More on this over here, for example: https://github.com/Microsoft/vscode/issues/16131

Hey Charles, I've just read The Inerview: https://pwreview.com/series/interviews/featured-professionals/ryan-cramer/ big thanks for that, too! My favorite messages in it: "...just go with the flow..." "...working through the issues... ...it's about solving mysteries..."

@matjazp Thanks for the info! I am going to evaluate it in this case.

Yeap, I did realized that too. If one needs PW's out of the box pagination support, simply filtering with if($page->viewable()) is just not enough, it can only be used as a last resort to prevent information leakage but that does not necessarily mean issue-free code. The approach I came up with in a nutshell is (besides using PW's built in access control): Hooking after Page::viewable with custom access checks and using if($page->viewable()) where needed. Hooking before Page::render with custom access checks, in order to block certain page access cases. Added hook method (Pages::siteFind) which delegates its task to Pages::find but before doing so it modifies the selector string based on certain conditions in order to prevent fetching certain records in the first place. However, my approach is rather crude and hardcoded into the site, so there is a lot of room for improvement here. I do not know if I should spend the time on evaluating DynamicRoles as I do not have too much time to waste, but what makes it compelling is this bit I read in Ryans intro: "This module directly affects the results of all page getting/finding operations by applying the access control directly to the database queries before pages are loaded. As a result, it is fast (regardless of scale), pagination friendly, and requires no further intervention by the developer other than configuring the dynamic roles as they see fit." Anyway, if you guys no longer use DynamicRoles with current versions of PW, then may I ask what other approach you use? Any guidance would be appreciated.

Thanks for the reply! Maybe others can chime in? Anyone out there using Dynamic Roles in production?

Hi Adrian, Thanx for the reply! Actually, it is probably me who needs Dynamic Roles. So do I understand it right that the fork of @matjazp is ok to install in production? This weekend I worked on implementing some sort of dynamic roles just to see how far I can get and also to study at least the basics in this area. However, if this fork is quite OK to use then it should be the way to go, I think. Side-note: it's a pity that Ryan left Dynamic Roles in the dust ?