szabesz

It's hard to tell without some sample code. Can you provide us with a shortened example of how you are constructing your output?

Here is a good one which I recommend for @Steve_Stifler to get started: https://www.pwtuts.com/processwire-tutorials/alternate-template-strategy-using-a-single-output-file/ I linked to this one this time because it also explains a simple strategy to get organized right from the beginning. The only thing I would do differently is that using relative paths in PHP can be cumbersome for beginners, so for example instead of this: include("./views/{$page->template->name}" . ".php"); I would use: include $config->paths->templates . "/views/{$page->template->name}" . ".php";

I see, thanks for the quick reply! Yes, disabling AdminOnSteroids "makes it go away". I thought it might be some sort of issue I must be aware of. I can live with it, I mean because the site will not have another language just the default plus English there will be no other translations to switch to. BTW, would it be possible to somehow show us what is modified/added by AOS? Maybe by hovering over the element and by waiting for a few seconds? Something like: https://codeburst.io/css-tips-and-tricks-using-pseudo-class-fa83248bb6e0 I'm just thinking out loud. I know that it is easy to disable AOS but in this case I was not even aware of the core features so I could not tell them apart.

I might have seen a multilingual newsletter once in my life but I might be wrong, so in my experience multilingual newsletters are very rare.

Hi @kixe Thanks for this technique! I followed your instructions and it seems to work as expected, however I get the following message on the translate page, maybe you or someone else can explain why and/or what it means: see the screenshot: Any ideas? Thanks in advance.

Hi @Steve_Stifler Please do not post the very same question in deferent forum sections. Regarding the answer to it, you can learn more about it in Using template files in ProcessWire in the docs.

Hi, One can set such a header entry like: $mail->header('Reply-To', 'my@replyto.address');

Hi @Gadgetto I am sorry for not being able to help but could you please make your thread more readable by "hiding" long code in "Spoiler" blocks (which can be added by clicking on the "eye icon" in the toolbar of this RTE)?

Sounds great! Are you aware of @adrian's Page Protector module which is somewhat related? BTW, thank you for all the effort you to put into sharing and supporting this module!

This reminds me that we have a recent discussion of "how to put count into good use": https://weekly.pw/issue/248/ : "exact match queries using Page reference fields"

Thanks for the additional explanation! I am after something like this:

While ProcessWire is capable of doing this right out of the box, you might find that without additional extra coding, the built in "free" modules will not perfectly fit your particular needs. If you do not want to spend time on learning how to code for the admin, you might want to consider purchasing these two modules from the main developer of PW, namely Ryan: https://processwire.com/talk/store/category/9-listerpro/ https://processwire.com/talk/store/category/7-profields/ With these two modules you can add easy to use and configure (meaning click-and-play) extra GUI possibilities to the backend which will surely enhance CRM like usage. Side-note: while these modules can be very useful, you might still need to add some extra code to support your needs, but this forum will be here to help, because it is full of sample code snippets and helpful fellow developers ? Note that these modules can be used for years without paying for upgrades becuase in the case of ProcessWire the need to keep things updated is mainly because of PHP moving forward, not because of anything else. So there is no need to pay yearly which is the case in the WordPress world, for example. In the case of Ryan's modules, you are allowed to pay upgrade price any time in the future. You can read more about this here: https://processwire.com/blog/posts/pw-3.0.80/#pro-module-renewals Also, as ProcessWire is secure, there is no driving force to upgrade the core either.

Welcome to the forums @Steve_Stifler I'm sorry for not being clear, I did not mean to "indoctrinate" you, I just did not have time to write a longer post yesterday. Sure, it takes time for newcomers to memorize forum "rules", that's quite ok. BTW, if you feel like becoming more like a frontend developer, then ProcessWire is probably the best way to go that route. Just check out our tutorials and beginner guides to get a bette picture of how ProcessWire site are built. You are quite right regarding this. Also, besides "freedom", it is quite easy to get started and there is a relatively easy learning curve ahead too.

How helpful of them ? ?. Typical reply of hosting providers when they happen to screw up something and they just do not want to advertise it.

Also: did you test it with various browsers, preferably without browser extensions being enabled?

In addition to what @bernhard wrote, this forum section is for module developers to support their own modules and not for general – module related – discussions. This topic belongs to the Getting Started section, so any moderators reading this: you might want to move it.

Hi Teppo, I do not remember correctly, but maybe after switching a site from 7.0.x to PHP 7.1.x I started to get a lot of these: PHP Notice: Undefined index: Previous page URL in .../ProcessChangelog/ProcessChangelog.module:810 Could it be possible to get rid of these?

I think Ben's "specification" is just somewhat vague so that is the source of our confusion. Anyway, Members Messaging can be either for frontend or PW's backend or even for both but in the latter case it would probably be practical to split the code among "submodules".

I think so, making use of the Comments module sounds like a really good idea. The youtube link I posted was just about the "dashboard like" behavior but besides being able to post announcements some simple conversation would be nice to have too.

I can tell you how to transfer me the $9995 you could not get rid of, just PM me ?

Thanx for the help! Module refresh did not help but saving settings did.

Hi Adrian, Recent Tracy versions do not work in the backend (the issue also prevents admin login), the "errors" I get (PHP 7.1.22): I tested a few old versions and TracyDebugger-4.17.10 is ok, while TracyDebugger-4.17.16 has this issue, so something between these two introduced the problem. I reverted back to v4.17.10 for the time being.

I would because Ryan did not wrote in his blog post that it is a requirement not to move the 404 page. Yes please ?

Maybe watching something similar helps: https://www.youtube.com/watch?v=_d0hZ8iS344 I'm thinking of logged in users being able to post messages in the PW backend which supports remote collaboration, or support developers by providing some means to announce changes made to the site. Currently if users want to communicate, PW does not support them at all.

Hi Ben, I'm still interested as long as it is also about admin side messaging out of the box.