szabesz

Probably the last report of it: https://processwire.com/blog/posts/pw-3.0.62-master/ I guess it is put aside a little bit since UIkit 3 is still in beta and seems to be changing here and there. It is wise to wait for the first "stable" v1 version in the case of something as complex as the ProcessWire admin.

@Neeks Did you try changing PHP/MySQL version of the site? v3 might choke on something that was ok with your current server setup.

How about both worlds?

@maxf5 Did you try it with <pw-region> too? Sure, they should be the same, but still... To tell the truth, I never really understood why having all these variations of the same thing is good. It just makes things more confusing, more time to debug but adds no additional feature. It's like having similarly named methods doing the same thing. Well, at least they are supposed to do the same

more ideas: https://modules.processwire.com/modules/fieldtype-yaml/ https://modules.processwire.com/modules/fieldtype-matrix/ ProFields: Page Table in the core.

Would be great to see a working example. An exported site profile maybe? Thanks advance!

Hi @Gideon So You might want to ask Hostgator's support since this issue is probably server related. As for .htaccess, I have no idea what the source of the error message can be, but apache should look for .htaccess in each directory or else how could it interpret them? Sure enough, if you have no such file there, then it is strange to see such a message.

Sure, you are right, there is and in my post I just briefly mention how to deal with addon domains because in my experience they are easier to manage since if one uses cPanel's "Create an Addon Domain" feature then by default the domain server will point to the given document root directory and all is setup well. At least in a properly configured cPanel account of course. So I really never had issues with addon domains. That is why my blogpost is mostly about how websites of addon domains and the website of the main domain can live happily together side-by-side in subdirs of public_htm/www. Regarding your issue, is seems to me that your files and directories do not have the permission/owner settings your server requires. Did you check those? EDIT: probably this is the most extensive guide we have in the docs: https://processwire.com/docs/security/file-permissions/

Hi, The short answer is that you can't. The long one is that ProcessWire site profiles are not like themes you can just simply replace. You need to refactor your current template files. Or am I misunderstanding your question perhaps?

Yep, it does not. Maybe because config.php is already included? I should check it Anyway, because of such issues I recently switched to using __DIR__, eg: require_once __DIR__ . '/./creds.php';

include_once "creds.php" and similar do work for me. Maybe is it something about your setup?

Hi, I guess you have permission issues. In my cPanel blog post I show my own setup, you might be interested in it.

Hi and welcome to ProcessWire, First of all, I do not think 10k+ sub-pages would be an issue for ProcessWire, but as the database grows optimized queries and caching are a must which is possible with PW, especially if your server is fast enough since you can delegate some logic to PHP as well when that can cut down on SQL queries. What you will not get with ProcessWire out of the box are things like "sales graphs, shipping methods & costs, order status, payment status (for bank transfers for example) etc..." Padloper can help you there but even Padloper is more like a skeleton then an out of the box solution. I've never used it but that is what I have gathered by reading about it. I have experience with WooCommerce and Magento v1, I wouldn't recommend any of them though. Magento is "over engineered" I think (they call it enterprise level, I call it unnecessarily complicated) and WooCommerce is just WordPress, so you know what it means... If you feel confident with Symfony then the alternatives you found sound viable options to me. I am working on a ProcessWire ecommerce site at the moment but I'm free in choosing external tools like Snipcart which is an alternative way to cut down on development. Hope this helps a bit. Others might join in the discussion with more info on the topic.

I should have gone to bed last night instead of... It does work indeed (PW 3.0.62) I was probably on the wrong page of the site to test it but around midnight it is sometimes hard to tell things apart Thanks for your help @thetuningspoon and @Robin S!

You mean this one? https://github.com/processwire/processwire/blob/master/wire/core/WireInput.php#L504 https://processwire.com/api/ref/input/http-url/ Does not seem to work. I get no query string. Not to mention the lack of urlSegmentsStr support, at least I cannot see it or looking at a completely wrong place... I dunno At least your snippet works fine. Thanks once more!

I have turned it into a Page method: /* Returns the complete URL of a Page. * * @param int arguments[0] Pass false to exclude the pageNum of the Paginator * @return string */ $wire->addHookMethod('Page::siteCompleteUrl', function($event) { $withPageNum = isset($event->arguments[0]) ? $event->arguments[0] : true; $full_url = page()->url; if (input()->urlSegmentsStr) { $full_url .= input()->urlSegmentsStr; } if ($withPageNum && input()->pageNum > 1) { $full_url .= "/" . config()->pageNumUrlPrefix . input()->pageNum; } $event->return = $full_url; }); Small changes were applied to it: "/" is added in the second "if" to avoid double slashes on the pages of the paginator first argument can be used to exclude the page number of the paginator, defaults to true

Could be turned into an optional core feature Thanks for sharing anyway!

So maybe it is me who has not spent too much time on it? I see what you mean now. Yep, I guess the label did change but Page == Page Reference, so the latter is more appropriate.

Hi, I guess you just do not spend too much time setting up ProcessWire fields If you need a "Page field" you have to choose "Page Reference", it has always been the case since it stores references to Page objects not the Pages themselves. I guess Notifications is used by the Notifications Module but I've never checked it as it looks obvious. Hope this helps.

Regarding your first issue: and in mystyles.js: CKEDITOR.stylesSet.add( 'mystyles', [ { name: 'Warning Paragraph', element: 'p', attributes: {'class': 'uk-alert-warning', 'data-uk-alert': ''} }, { name: 'Success Paragraph', element: 'p', attributes: {'class': 'uk-alert-success', 'data-uk-alert': ''} } ]); This setup works for me in ProcessWire 3.0.62. Is it what you are looking for? Also, something like this is my config-body.js: I have not yet worked with contents.css/contents-inline.css, it is still on my todo list...

I have just tested @owzim's other great module InputfieldAceExtended which works perfectly if we want to use syntax highlighting for YAML. However, @Robin S's suggestion to fix the error changes the Details Tab, making it impossible to configure the InputField Type as seen in the screenshots below: original: after applying the suggestion:

Aha, yes! Thank you! I keep forgetting that we have unformatted values too. I updated both methods in my original post. Cheers,

Hi @Zeka Sure, however the most convenient way to do it is "just to save" what you've put together in the admin. Besides, site editors could do it too, just like working with Find's Bookmarks or ListerPro's Listers.

Thank you @ryan, pretty impressive so far! Just one question: are we going to be able to save "presets" too? So that predefined export/import settings can be made available when needed.

@owzim Hi, any chance of applying this fix? Thank you in advance.