wbmnfktr

Can confirm this behaviour.

Ok... is test nowadays somehow... protected within page names? I know about issues in field names (back in version 2.whatever.x) but not in page names.

That's weird. Especially as most/all pages within Trash will be re-named.

Ok... well... that's kind of easy as well - or it should be at least for you. As you used Bitnami there should be a dedicated Bitname folder somewhere now. C:\Bitnami User>Bitnami Something like that I guess - I'm not sure as I don't use Bitnami. But... within that default Bitnami project (ProcessWire) folder you will find a folder called site and within that a folder called templates. So... it might be C:\Bitnami\Processwire\site\templates

You could edit the output in the template file and use the new $page->if() method. https://processwire.com/api/ref/page/if/ So there might be no real need in setting a real value. Add a note or description to tell and explain editors the field behaviour. You could define that default value somewhere in your config.php or even in a dedicated settings page to keep it editable - at least for superusers.

Does a clone/copy of that page end in a 403 as well? Are there any hooks or if/else statement in your template that check for specific user roles? Can you find more details in the logs?

In that tutorial - look at step 8. The Template File Step 8 – Outputting dynamic data in your template file While still in the page editor from step 7, click the "View" link to see your page. Note that it still says "Happy planet" for type (rather than "Terrestrial planet") and "Millions of years" rather than "4.54 billion years". That's because the page is still being rendered with just the static data in it. We need to update the template file so that it recognizes the fields we added and outputs the values of those fields. Edit /site/templates/planet.php and replace the static text in there with tags like this, replacing field_name with the name of the field:

In addition to that I wrote this: https://copypaste.pw/howto/author-box/ Maybe it helps or at least gives you directions.

If I remember correctly that has to be enabled in Mailchimp first. Allow someone to re-subscribe again.

301 are totally fine - for ProcessWire and Google. Nothing to worry about. Read next part - as you have almost nothing to do for this. ? The existing ProcessWire .htaccess file already has this in place. Uncomment two lines and you are ready to go. # ----------------------------------------------------------------------------------------------- # 13. OPTIONAL: Redirect users to the 'www.' version of the site (uncomment to enable). # For example: http://processwire.com/ would be redirected to http://www.processwire.com/ # ----------------------------------------------------------------------------------------------- # RewriteCond %{HTTP_HOST} !^www\. [NC] # RewriteRule ^ http://www.%{HTTP_HOST}%{REQUEST_URI} [L,R=301] You can just add those fields to the user template - which can be found in Setup > Templates (after enabling showing system templates). And of course you have to create those fields first - if not already created. Setup > Fields There you can create all kinds of fields. Text, textarea, image, whatever... I recommend doing the tutorials available here: https://processwire.com/docs/tutorials/ They will help you to understand ProcessWire. It's absolutely not a waste of time. Even as someone who never worked with ProcessWire, but having some basic knowledge in terms of PHP, can learn ProcessWire within a weekend.

One image is actually indexed... ? There are a few things you might want to change or at least take a closer look at. use only https:// and redirect to it choose prefered domain (see below) reduce page size drastically (~13MB is too large) and speed it up remove the preloader as it stays for hours fix your sitemap (as mentioned by @dragan) set up Google Search Console to figure out problems with your site add robots.txt (as mentioned above) and reference your sitemap and maybe add a nice favicon.ico Your site is available through 4 different addresses: http://lobo-taberna.de/ http://www.lobo-taberna.de/ https://lobo-taberna.de/ https://www.lobo-taberna.de/ Choose one. ? Reduce page size to ... way less than that.

I might miss it but how do you add tags and categories to a page? If you are using a page field (PageReference) you could just find() them. foreach( $pages->find("tagFieldName=$tag") as $pageWithMyTag ) { // whatever you want }

Imagine you have a nice conversation with someone and only a few hours afterwards you are knee-deep into a module and possibilities you never thought of. Thank you @bernhard for hijacking my plans for the weekend. ?

The login to add/edit the profile as well. Redirects after login attempt to https://login/ .

On Github is a .txt file, that correct. But its content should work just fine. NEVER delete a file you might need again. Especially while debugging. So as the new .htaccess doesn't as well... what were the last changes you made? Did you install or change files aside from .htaccess? Did you move folders? Did you enable anything in your hosting panel? It seems you tried to install SSL. How did you do that? Via hosting panel? Manual cert files or something similar? One change in the .htaccess can potentially break everything but it can always be reversed.

Rename the old htaccess file and just add a fresh copy from the Github repository.

Outgoing link tracking is possible with Google Analytics, Google Tag Manager and Piwik. You could also create masked links with the Jumplinks module. It counts clicks on each Jumplink. You could combine these two methods to track a much broader audience.

I don't know if this hook causes the error. Test the registration without that hook to confirm it. Your modules seem to be fine - I guess. Unless you don't use a weird setup with nginx or frameworks of any kind (no, not materialize.css ?) I have no idea where this comes from.

Do you have any custom code somewhere? Maybe in ready.php? Really can't tell where this comes from. What modules do you use? Which version of ProcessWire and PHP?

You're welcome. ? I wouldn't create a fresh installation... just start taking things apart. Check your page reference field. Maybe there are no pages, maybe they are hidden, maybe your input type is wrong, maybe whatever. Check if you added the field to the user template and to the module settings. Try another browser, delete your cache... if there were any errors they should show up. Maybe you will find something in your dev console.

Just installed Login/Register/Profile module, created a page reference field and a select options field to test, added both fields to the user template and the module settings, added the module code to a template and it worked. Maybe me screenshots help in some way.

If the job needs to be done just download all files manually or try Site Profile Exporter. Some tipps and details on how to migrate manually can be found here: https://processwire.com/docs/security/migration/

I love their idea of minimal code and uncluttered but yet customizable tools. I recently set up a machine with Linux again to find out if I could establish a more solid workflow than on Windows. After several tests I finally decided to go with Ubuntu 19.04 and the Gnome desktop. It works pretty well so far. On another way way older machine I run Manjaro with i3 and hopefully soon some suckless tools. It's amazing how well that old Thinkpad X201 performs with that kind of OS.

Just in case: suckless.org > surf = http://surf.suckless.org/

@louisstephens I just send you a message - attached to it the whole script.