szabesz

Yes it does

Have you seen these? https://processwire.com/talk/topic/11451-change-default-language-revisited/ or: https://processwire.com/talk/topic/12743-using-an-empty-language-pack-as-the-default-front-end-language/?do=findComment&comment=116016

I'm not a fan of docs as part of modules. Maybe its just me but I like to keep the codebase as light as possible. Also, we've been asking for "changelog" support in ProcessWire so it is hard to see why docs support would get priority but one never knows I understand this but if that tool can export in a format which makes it possible to migrate the whole stuff – just in case – then why not give it a try? I'm not pushing penflip.com as I have only read its homepage, I just like tools which are designed for a specific need. As long as they work well, of course...

we

+1 I'm not fond of unsupported "hacky" solutions but it is just me Maybe a dedicated tool instead? I just googled a bit: https://www.penflip.com/ There could be alternatives, of course.

I do not know what makes a genius but Steve Jobs was a rather controversial character. Sometimes he was more like maniac. He was rather good at expressing his thoughts, sure. http://fortune.com/2008/03/05/the-trouble-with-steve-jobs/ "Jobs’ personal abuses are also legend: He parks his Mercedes in handicapped spaces, periodically reduces subordinates to tears, and fires employees in angry tantrums. Yet many of his top deputies at Apple have worked with him for years, and even some of those who have departed say that although it’s often brutal and Jobs hogs the credit, they’ve never done better work." In my point of view, a "true genius" has no moral issues to begin with. After all she/he is supposed to be a "genius", right?

@adrian Hi, I scanned the "docs" and could not find this tip of yours: https://github.com/processwire/processwire-issues/issues/429#issuecomment-342976462 sounds like an important one. Could you please consider adding it? Also, AJAX instructions are mostly in the Getting Started section which is fine but probably a dedicated "Debugging AJAX" or maybe "Working with AJAX" section with links to other related tips found on the page and additional tips like the one above would be nice to have.

Thanks for clarifying!

Nice work, thanks for the showcase. Are you aware of "Lorem ipsum..." still being used on stellardebating.nicegrp.com pages?

Hi, https://processwire.com/api/include/ These two are equivalent, so what syntax you prefer to use is up to you: $mypage = $wire->pages->get("/about/contact/"); $mypage = wire('pages')->get("/about/contact/"); wire('pages') As far as I know, only this should work, so they are not really "equivalent" in this context. See for example: https://processwire.com/talk/topic/13977-custom-php-code-selector/?tab=comments#comment-125688 Am I mistaken?

And start your timer. You have only: Sorry for this, I could not resist

Thanks for sharing! This module can be quite useful

Do you have any idea where it can be looked up? I mean, where we can check what is probably(?) supported by most modern OSes/browsers these days? It would be interesting to know. I guess the "cross-platform" typefaces are more or less the same as they have ever been but those font files seem to keep growing by added characters as the OSes evolve.

That reminds me of this tool I've somewhat forgotten about: http://fontello.com/ More efficient? Hard to tell... Maybe a custom set? Thanks in advance!

Hi, A related good to read post: https://processwire.com/talk/topic/13977-custom-php-code-selector/?tab=comments#comment-125688

Line-only versions are harder to do right because of its nature and limitations but I was thinking about going crazy with optimization regarding how much is injected into the page. By removing the probably not needed <title>turn-off</title> from my version (it was just exported too, as the name of the file was "turn-off") we have only 300 characters. Probably this is not the one where we can gain a lot but more complex ones like logos and such. I would be happy to do it. It is probably not worth forcing us to use line-only svg when more complex icons are needed but some of then (like this turn on/off icon called EnableButton) looks doable. Others might just need SVGO treatment I focused on EnableButton because I would like to see less in the source code of a frontend page when Tracy is disabled. So something like this (removing some line breaks) would be nice too: <style>div#TracyEnableButton{bottom:10px!important;right:10px!important;z-index:99999!important;position:fixed!important;width:16px!important;height:16px!important;margin:0px!important;padding:0px!important;cursor:pointer!important;}div#TracyEnableButtonsvg{width:16px!important;height:16px!important;}</style> I often use the Chrome extension called Quick source viewer which displays the actual rendered output in a different way then the inspector. For the styles I get the line breaks but if you could remove them we would get a more compact version injected.

@adrian This morning I quickly crafted my own version of the "TracyEnableButton" in order to see if a smaller version can be made. The idea is that – in such small sizes the icons are used – using only lines should be enough to get very similar results. Of course, when an icon like this is enlarged its line only characteristics become prominent but I do not think it is an issue in our case. So here it comes: <svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 54.48 57.24"><defs><style>.a{fill:none;stroke:#CD1818;stroke-miterlimit:10;stroke-width:8px;}</style></defs><title>turn-off</title><path class="a" d="M24,10.17a23.24,23.24,0,1,0,16,0" transform="translate(-4.76 -2)"/><line class="a" x1="27.24" x2="27.24" y2="21"/></svg> Only 323 characters versus 1101 (current icon). What do you think? Is it usable, and if so worth the effort? I could produce all the others if you think it is a good idea.

As long as you do not have security concerns regarding those files there is nothing to worry about. As an added precaution you might want to use htmlspecialchars() or better yet $sanitizer->entities() like this: $comments = $sanitizer->entities($sanitizer->textarea($input->post->comments)); $message .= 'Comments: ' . $comments; This is because $sanitizer->textarea() is for input – BTW, in your code you use $sanitizer->text() which is for single line only, so you might want to change it – while $sanitizer->entities() is for output which in this case will be performed at the email client's end. See this discussion for example (last comment at the bottom): https://stackoverflow.com/questions/17115426/do-i-need-to-sanitize-user-inputted-data-before-sending-it-in-an-email Sometimes it happens but I have not yet figured out when. Other times I get emails in "almost no time".

Hello, Are you talking about this perhaps: https://processwire.com/blog/posts/prodrafts-now-available-in-pre-release/#prodrafts-also-provides-automatic-save-capability ? Without the ProDrafts module, there is no automatic save capability

Double bother I need to think, think, think harder next time This is the first time I see these errors, probably I got intimidated... Yes please! The problem with this that I get the result in a not too tall box with lots of scrolling an clicking and the presentation of it is not as "good" as the one with the panel. What if there was a way to put custom settings onto the Panel Selector? Meaning module settings could be enabled/disabled for the Panel Selector, those one happens to switch on/of often. Currently I have no idea how the UI could be implemented for this, so this is just a blurry thought at this time.

I had the time to do some testing, here it comes (my MAMP Pro): API variables: 0.3ms Core Classes: 0.4ms Config Data: 270ms Version List: 14ms API variables + Core Classes + Admin Link + Doc Links: 0.9ms The result of d($config) is: Frontend: syntax error, unexpected end of file File: .../site/assets/cache/TracyDebugger/consoleCode.php:2 1: <?php if(!defined("PROCESSWIRE")) die("no direct access"); $page = $pages->get(1); 2: d($config) Admin: Same as above + 500: Internal Server Error: See the browser dev console for the actual error Why? It used to work. BTW, links in this Info panel do not not use _blank, why? I keep forgetting it which is kinda annoying after while. Is it just me?

I do not see how UIkit is a dependency here. Ryan has just shown us that he could replace the old skin with a new one in a relatively short period of time. UIkit 3 is currently a modern, easy to personalize "framework" on which experienced developers have been working for months if not years. How could the ProcessWire community build something better than that? Without some sort of framework there is no documented/conventional way to implement things which makes it hard (if not impossible) to adhere to some sort of "standards".

Thanks for the tip, I think generally it is the way to go, however, I would like to add a few comments: It can be useful if there are "permission issues". Do not forget httpHosts either and other settings might be important to change too. .htaccess might also be different on staging and live (production) so proceed accordingly It should not matter which step it is.

Hi @adrian, I've just updated to v4.7.6 – skipping a few versions altogether – and my current interest is in the ProcessWire Info Panel. I noticed that turning on API variables, Core Classes and Config Data does have an impact on page load time, as expected. Panel selector reports 300ms vs 14ms (frontend with not to much on it). However, System Info's page load time report doesn't change at all: always about 260ms, no matter what is enabled for the ProcessWire Info Panel. 260ms is less than 300ms, so I wonder how these numbers are related in the first place? I also have a request regarding this ProcessWire Info Panel. Since "API variables, Core Classes and Config Data" takes a considerable time to load, it would be great if we could keep them turned off by default, and temporarily enable them just like the panels themselves (Once, Sticky) but this would be an overkill, I think, so maybe moving them to their own panel would suffice. I mean, I normally don't need them but when I want to peek under the hood they are very helpful indeed. I also tested page load time just by watching Chrome's loading animation and it is indeed a lot faster to load the page without them, so there is a good reason to keep them off. However, going to Tracy's settings to turn them on/off is time consuming. What do you think?

I would have thought that nearly all new site developments use PW3. I know I have never contemplated building a new site with the old <= v2.7. And most buyers would be using VPS for new projects rather than retrofitting it into old projects that they are not willing to upgrade, wouldn't they? @kongondo You could run a quick survey. Personally I agree that it is not likely that VPS customers want it for PW 2.7 but it is your decision, of course. I started with ProcessWire 3 so anything before that is history to me. BTW: https://weekly.pw/polls/ see: Which versions of ProcessWire are you currently hosting or managing? (146 votes)