wbmnfktr

I can confirm this! Tested on 3.0.189-dev and 3.0.190-dev so far.

That looks way better and works almost as expected... at least in the frontend. Trying the EDIT page option results in an error. Full error:

Fully agree on this.

I just somehow ran into this problem and find no way to fix - besides importing and old DB backup (probably). Full error below: What did I do? Within that instace I installed a second language for testing purposes, edited the homepage so that it has /de/ (default) and /en/ (second language), changed the Languages Support - Page Names settings to redirect to the default language path (/de/), created some pages, tested, felt fine with it. Somewhere in-between I updated to the latest 3.0.190 dev and tested a bit more, did other stuff (frontend only, no API code or module dev), then deleted the second language and wanted to the change the homepage again... so here we are. All other pages with (former) additional content in another language work fine, can be edited and whatsoever. The main difference seems to be that the homepage contains a repeater matrix field with content that's only available in english (second language I deleted now). I always thought deleting languages is enough... maybe it isn't. Someone any ideas?

In a client-case... I would have done probably the same as you and posted here. Haven't looked through the forums but maybe someone had this issue as well. Can't really imagine noone else ever had this issue. But ok... maybe though. For my personal projects or projects I maintain... I'd go the easiest route for whatever it would be in those cases. Another idea... you could probably use $page->viewable() within the template.

I wouldn't say I'm stuck... but my clients could end in a dead-end for some reason (this reason). Most of my multi-language projects just show the default-language content. In case I use RepeaterMatrix (ProFields) the client or I can always add a single text-block that shows something in the non-default language and go from there. Right now I could imagine using a HannaCode block that lists all available alternative language versions... in your case it would be just the spanish version.

This doesn't indicate a properly working Apache for all scenarios at all. It's just the most basic startup screen you could imagine for LAMP setup. So... you installed everything in just one folder (/var/www/html/PROGRAMMSUBFOLDER)? No... set up VirtualHosts. That's a one-time-investment in a solid dev environment. From there... you could go in any direction. With ProcessWire, WP, Drupal, Typo3... whatever. That's the default behaviour when installing ProcessWire into a subfolder. While it works... I wouldn't recommend it. Only when you really know what you are doing, testing for example, or when you already installed Processwire 100 times. ProcessWire was ready to go. Your setup wasn't. Sorry when this sounds a bit rude but using a non-working or better to say not fully configured environment as a base for whatever kind of (web-) development and then blaming the software because it doesn't like it that much... is unfair. I can't and won't blame you but I want to move your focus to the reason for your experience here. It wasn't ProcessWire. Sure installation is sometimes a bit more than just clicking but in this case there were way more steps than really necessary. In case you want to experience a super solid installation that's a breeze... use something like Laragon on Windows, MAMP on Mac or ... let's skip the Linux part here. One last word here: Even though my response here could be read a bit harsh... I really appreciate that you stayed the whole way, worked through everything from start to finish. And I wish and hope you start to love ProcessWire like each and everyone here in this thread and community.

Editing the link within the dialog or in the source code - like you. Yet... I never had this challenge before so far. Tried this now out of curiosity. Don't know any other way right now. WOW!

As this module was just recommend to me I had to give it a try. Got the necessary API keys and grabbed the latest copy from Github. The result so far: Double checked the entered credentials, picked some templates and ... I'm running the latest PW 3.0.189 here and have to remove the module to bring the site back to live.

Short URLs VS Flat URL Structure Does URL Length Affect SEO? https://www.searchenginejournal.com/does-url-length-affect-seo/425230/ Google: No Benefit to An Artificially Flat URL Structure https://www.searchenginejournal.com/google-no-benefit-to-an-artificially-flat-url-structure/400609/

Well... https://github.com/Toutouwai/VirtualParents

@Gideon So that happens sometimes... ???

Hey @Gideon So... why should I? My setup works perfectly fine. ;)

Can you please post your Apache2 host/vhost configuration file. Especially the <Directory ...> part could be interesting - as this is crucial in most cases. My configuration looks like this: <VirtualHost *:80> ServerName pw.test ServerAlias www.pw.test pw.test DocumentRoot /home/YOURUSERNAME/www/pw.test <Directory /home/YOURUSERNAME/www/pw.test> AllowOverride all allow from all Options None Require all granted </Directory> ErrorLog ${APACHE_LOG_DIR}/pw.test-error.log CustomLog ${APACHE_LOG_DIR}/pw.test-access.log combined </VirtualHost>

I worked with those (VirtualBox, VMWare) that's why I asked. ? Really can't imagine doing so but hey... if this work's for you, I'm perfectly fine with this. Just wanted to make sure I understood that correctly. I'm glad I can keep one machine up and running with my toolset.

You really have a virtualmachine with Windows for each and every project you work on?

First of all... Welcome to the World of ProcessWire. I don't know anything about the site-profile you are using. I've seen it but never worked with it. Resizing an image can be done in various ways. You either upload it in the correct size already, you resize it in the backend or define a size within the template code through the API, finishing touches in CSS and so on. What you describe sounds a bit like that you are not only new to ProcessWire but maybe even to webdev - both is fine. BUT... I highly suggest you take a look at the ProcessWire Tutorials which guide you through a lot of steps. Videos are nice but those aren't anything like tutorials (at least those I know about). The site profile will give you a nice starting point but you won't end up with a highly customized version of just from using the backend or settings in it. You will have to tinker around with the template files, the CSS and might even have to complete new markup.

Nice one... it's amazingly fast even though there are tons of images. TTFB is almost instant. Where is the site hosted and what kind of hosting is this? Standard webhosting isn't that fast usually. Another funny side note... I know this company and actually have bought some of my suits and wardrobe there. Funny how small the world is. That's weird!

In other news: Color-coding content blocks is such a great addition. Even those who don't use the backend that often find the right spot way easier now. Thanks @Ivan Gretsky for the idea and @ryan for adding this to the latest dev branch.

Question to all of you... What about a setting that enables PageAutoSave O N L Y when in PreviewMode? I play a lot with Page Autosave + Live Preview but sometimes I'm just tackling my daily tasks and the auto-save feature is (kind of) too much as I start writing but can't finish the text due to a phone call, "writer's block" or my empty coffee cup. Yet the content was entered, saved and is available on the frontend for page visitors. Luckily only within a side project at the moment but still. I could enable the feature only for unpublished pages but most of the content that gets edited is already published and therefore live-content. I'm almost missing a setting like "enable autosave only when livepreview-window is active". What do you think?

Besides that... the homepage is HUGE.

Probably...

Maybe I can take some time and look how to customize your module. Right now I use a hook for this kind of maintenance. While it's using template and fields it's not that easy to update like your module. On the other hand changes are documented.

Thanks @Robin S. I'll add those settings/permissions to my modules later on. Just in case. For 3rd party modules I might to keep it a bit more future-proof. Thanks @BitPoet. Your untested but working code was the solution for my upcoming problems here. That it's safe for future updates is one of the best parts.

In case you use Neovim/VIM you can still use this VSCode extension through coc-snippets.