szabesz

How about <= 1 ? One never knows...

Quote from page 9 of the book: "Technical debt, the eventual consequence of poor system design, is something that I've found comes with the career of a PHP developer. This has been true for me whether it has been dealing with systems that provide advanced functionality or simple websites. It usually arises because a developer elects to implement a bad design for a variety of reasons; this is when adding functionality to an existing codebase or taking poor design decisions during the initial construction of software. Refactoring can help us address these issues. SensioLabs (the creators of the Symfony framework) have a tool called Insight that allows developers to calculate the technical debt in their own code. In 2011, they did an evaluation of technical debt in various projects using this tool; rather unsurprisingly they found that WordPress 4.1 topped the chart of all platforms they evaluated with them claiming it would take 20.1 years to resolve the technical debt that the project contains."

Thanks for the advice! Yeah, I know that Design Patterns are not something that should be forced no matter what, especially when dealing with CMSs like PW. That is why I used the word "study", because I guess I will get a better understanding of PHP by reading this book. Also, Design Patterns are not new to me, back in my ActionScript 3 days I read a lot about them and that helped me there too.

Thank you! I've just downloaded it and skimming through the pages I can see that I must study this book

I do hope things will clear up a bit in the coming months but do believe there will be a lot of pitfalls and businesses are not prepared at all, as lots of them not yet even heard of all this. If small or micro sized companies go out of business because of the fines they need to pay then we as developers will have less-and-less business opportunities and not more...

Sure but since it is impossible to fully comply we will be held liable. I do not think it is a clear and bright situation at all. Lot's of micro and small business cannot afford to fully(?) comply even if they do not sell nor abuse personal data and never experienced security breaches. As I stated before I'm not saying that there is something wrong with the intent of GDPR and ePrivacy. The "only" issue with them that it is impossible to fully comply, and only biggest companies have the resources to defend against legal attacks because of this situation coming soon. You have your own website and/or blog too, right? Isn't that an online thingy?

http://www.osborneclarke.com/insights/regulatory-outlook-data-protection-and-privacy-january-2018/ Fact 1: GDPR will take effect across the EU from 25 May 2018. Fact 2: as of 19 January 2018: We can expect the Article 29 Working Party to publish its final version of these guidelines over the next few months. So we need to comply to the impossible in time, but only within a small timeframe. Will they publish the "final" versions in time, I wonder? And some more time killers "if you do not have" anything to develop today : https://www.bima.co.uk/Article/2018/02-Feb-2018/Here-comes-the-European-ePrivacy-Regulation--the-GDPRs-forgotten-sibling https://digiday.com/media/winners-losers-eus-new-eprivacy-law/ http://www.businessinsider.com/gdpr-europe-privacy-law-advantage-to-us-tech-companies-2018-2 https://www.businessbrew.io/blog/understand-pecr-and-gdpr https://www.the-gma.com/eu-eprivacy-law

Unfortunately, as we dive into GDPR, there will be a lot more that will worry us! For example: It can even be our responsibility: "As a business owner you are a data controller. Your web developer, hoster and saas marketing tools ( mailchimp, salesforce etc. ) are data processors. The data controller is ultimately responsible for the protection of personal data they store. However if it is found that your data processor has been negligent then they are also responsible." Since server logs cannot get any extra protections pretty soon, are we going to be negligent out of the box? Hosters must also comply. Without them a site cannot comply. If the site does not comply because of us/hoster, are we negligent? What does being negligent mean, anyway? This is the sort of ambiguous stuff which is frequent in any text written by lawyers and such. What about an order form with AJAX updating data? When should we get the consent during the not linear data post process? With recent trend of data fragments being sent constantly, is it technically possible to ask the user in advance in any case? I would not ask the user on each form as it is a UX killer and silly. I am thinking about placing an impossible to miss "GDPR banner" on the site, where all stuff is explained and probably the first form submission is only possible by going to that page (+ also a link to that page from the form...). If users know where they are informed, and they also click that one and only checkbox on purpose then this part of GDRP should be covered. And this is the sort of module that could also be written. I'm thinking of producing required legal text fragments which can be turned on/off depending on the site's needs. That text should be editable of course. Such a plugin could be just a starting point, which help us not to forget things.

ugh-ugh, so many bored developers trying to cheer up themselves...

And that is why companies will not be able to fully comply even if they wanted to. Most people cannot even find an old email, they do not properly know how Outlook works, and on top of that they use Windows, the most hackable widely used OS on the planet. So now what? While the intention of GDPR is OK, it has been written by lawyers who live in their dream world not knowing anything about IT. Do they care if they ask the impossible? Of course they don't. Anyway, we need to do our best, so I propose to start writing a module that helps generating the legal stuff (privacy policy, etc...) that must be outputted somewhere so we do not have to reinvent the wheel. For other systems people are already writing plugins that test the CMS and look for possible issues, eg: https://www.opencart.com/index.php?route=marketplace/extension/info&extension_id=32993&sort=date_added https://wordpress.org/plugins/tags/gdpr/ I guess none of us wants to spend a lot of time on it, so why don't we help each other?

For such a site it must be taken seriously as GDPR tries to differentiate the "level of security measures and the fine to pay in the absence of proper compliance" – so to speak –, meaning that security measures applied to data collection and handling must align with the amount of data and its sensitivity. I guess your client will need a "GDPR professional" to make it right. The websites I deal with require less work to comply but it is sill something what will add up to lots of ours of work on my end.

GDPR itself is mandatory, but there was a confusion about storing personal data in an encrypted way only as it was supposed to be necessary to comply. Being a European developer, I will spend a considerable amount of time to help my clients out with GDPR and I'm still learning the details... However, this encryption issue seemed to be a huge technical problem if it is mandatory. Since it is not, now I can concentrate on the other issues GDPR generates. I think this confusion about encryption was the biggest issue so I though I would post some links to show that is in a non-issue after all. There are good resources about GDPR about there, but here is a brief introduction to check out first: http://ec.europa.eu/justice/smedataprotect/index_en.htm Also note that: "Where does GDPR apply? If you sell any products to customers based in the EU, or have EU visitors to your site, you’ll need to make sure your site complies with GDPR. It applies to all 28 EU member states and to entities and organisations outside the EU when processing the data of citizens within it. IMPORTANT to note: Google Analytics and others ARE personal data collectors too! Eg: Statistics apps like cPanel apps, similar CMS plugins, custom solutions like Piwik", etc. And this means not European websites should also consider complying to avoid yet to be seen possible legal issues. The good thing is that the silly automatic cookie consent does not seem to apply anymore, as setting cookies is not data collection in itself. In GDPR there is only one sentence where cookies are mentioned: https://gdpr-info.eu/recitals/no-30/ And it is just about listing a few technical possibilities of possible personal profile building. However, if there is no profile building – meaning there is no data collection this way – then cookies are non-issues. I still need to read up on this one, but this is my current understanding. Of course, if cookies are used for profiling then it is a different story and they must be considered when dealing with GDPR. There is a lot to consider regarding GDPR. As you can imagine, complying is a time consuming process, a real PITA

"GDPR: Encryption is NOT Mandatory!" https://www.linkedin.com/pulse/gdpr-encryption-mandatory-gary-hibberd "Although under the GDPR encryption is not mandatory,..." AND "Before doing so let’s be clear: GDPR compliance, as we wrote before is a business strategy challenge and encrypting personal data STRICTLY SPEAKING is not mandatory." : https://www.i-scoop.eu/gdpr-encryption/

How to track it down? Every now and then I get it too but so far no luck figuring it out and everything seems to running without issues. It's hard to fix something which does not seem to be broken.

Thanks Adrian! Luckily he was held up by the "technical issue" so I could watch it live. So this is a PWA: https://stenciljs.com/ It IS performant but these early PWAs look rather poor on a desktop. Demos: https://stenciljs.com/demos They simply look like blown up mobile apps, but it is surely just the beginning...

So, I am told...but at the cost of what? You get a slower app? Just what I've read. But the point about using technology you already know (HTML, etc) is a good thing (most times). Yeah, pros and cons. It all depends on what you want to develop. For games, being native is the best option but anything else can be ok built on Cordova. "Speed" (regarding both app performance and development time) highly depends on the framework(s) being used. I do not really have a lot of experience so I am not the one to get into deeper details, I just wanted to draw attention to a few important points.

Sure, but as Adrian said the core and its plugins are "native". What else could they be? Last time I built an app with Cordova was 5 years ago and it was pretty problematic but it worked for sure. I guess since then things must have matured a lot and naturally developing hybrid apps takes a lot less time, also you do not have to learn Java, Swift, Objective-C, "all at the same time" but you can put to use a great deal of knowledge you already have. Last winter I googled around to see what is available to ease Corodva based development and by spending a day on the research I concluded that ionicframework.com is the one I would pick. No project in sight for me though, so I stick to PW these days

Do not try to be more creative than they are! They might take it as an insult I like the site too, btw. Some big images were a bit slow to appear and the hamburger menu is a bit too small but all in all it is a very nice site!

Have you already considered using the Changelog module by @teppo ? http://modules.processwire.com/modules/process-changelog/ It might help.

Hi, Since I have ListerPro, I use that to change the defaults. Sorry if it does not help, maybe some else can can provide another solution, not requiring ListerPro.

@Maxplex Did you use this one by any chance? https://modules.processwire.com/modules/duplicator/ Duplicator should work but as @Robin S pointed out, manual cloning of the site should work too. I used to install a few sites at 1&1 without issues.

Another issue report: Right after installing and accessing Duplicator's Package Manager, when no package has ever been created: 2x PHP Warning: filesize(): stat failed for .../site/assets/logs/duplicator.txt in .../wire/core/FileLog.php:225 1× PHP Warning: filesize(): stat failed for .../site/assets/logs/duplicator.txt in .../wire/core/FileLog.php:237 1× PHP Warning: file(.../site/assets/logs/duplicator.txt): failed to open stream: No such file or directory in .../wire/core/FileLog.php:238

I see. However, it just "fails" silently. Maybe a notification to the user? Or did I get one just missed it?

@flydev Hi, I was fiddling with the package name config and accidentally created one package named like this: 2018-02-05_21-16-00-{timestamp}_mysite_loc.zip.package.zip I could not delete it with the Package Manager's trash icon + clicking the Delete button of the confirmation dialog (nothing happened). Maybe because of the curly brackets?