Jump to content

dotnetic

Members
  • Posts

    909
  • Joined

  • Last visited

  • Days Won

    9

Everything posted by dotnetic

  1. I could not have it said better than @MoritzLost did and totally agree. But maybe you can move your post to the new thread?
  2. @Malinda Do you have the admin username and access to the files on the webserver? If so, you can following code to one of your templates, and set a new password for the admin user. Then you can log in with admin and the password you have chosen.
  3. The problem: Synchronizing fields and/or templates made on the dev server with the live server is cumbersome. At the same time, there is no version control of fields and templates, which some folks (including myself) see as a disadvantage of ProcessWire. A way to have version control to track changes and replicate automatically would be desirable. There is the template and fields export feature in ProcessWire which has said for ages that this is only a beta version, although I have used it many times without any problems. However, even with this method, it is very cumbersome to reconcile changes between dev and live. You have to remember which fields / templates you created and select them, then copy and paste them on the dev server. This is a manual, cumbersome and time consuming process. Existing solutions: For this reason, several solutions have been developed such as: Migrations by @LostKobrakai https://processwire.com/talk/topic/14603-rocksvn-brings-version-control-to-your-fields-templates/ ProcessWires Template's and field's export function https://processwire.com/modules/rock-migrations/ https://processwire.com/talk/topic/25307-oh-no-not-another-migration-module/ https://processwire.com/modules/auto-export-templates-and-fields/ Other systems like Laravel, Craft, Kirby and Statamic use configuration files (migrations, YAML) to manage fields / templates, which allow to create a state of fields / templates. Since the configuration is done in a file, you can of course manage it with git (or other vcs). By configuring in a file, it is also possible to automatically execute these migrations during a git push through different deploy pipelines like github actions, buddy, bitbucket pipelines and thus you have the desired state on the desired server. Where to go from here? In another post @bernhard showcased a prototype, that uses a YAML-file to create and manage fields / templates in ProcessWire. At the same time he showcased a YAML recorder which writes all changes that are made to templates and fields into a YAML file, which looks very promising: I think a combination of a recorder and a YAML config file would be a optimal solution, at least for me. What format to use for such a configuration file was and has also to be discussed:
  4. YAML is easier to read and write as PHP and less error prone (Yeah I know, we are devs, but there might be unexperienced devs / users that try to accomplish something fast). Indeed I agree, that PHP would offer more possibilities, but I think most times YAML or another configuration markup are enough. Every developer ist different here. Some might prefer writing directly to the file to change things or add new fields/templates, others prefer to do it via the admin. Update: I would like to shift this conversation to a newly created thread, because we are getting off-topic of sharing out setup/tools.
  5. @bernhard The YAML recorder and migration of the project.yaml look awesome. Any plans to release these additions to RockMigrations? I think this is a good way to make fields and templates version controlled. Having a feature like the YAML config and recorder added to the core would be a very good thing IMHO. The not programmable definition of fields and templates and migrating contents and structure to a live server is cumbersome (without RockMigrations) and led me to try out alternatives to ProcessWire in the past. I used Statamic and Kirby which both have configuration files for fields/templates, which can be version controlled and I really like the way it's done.
  6. @ryan Thanks for the added supported fields in the findRaw method. I am still having performance issues with my queries, but I try to find the bottleneck or might even provide you with a dump, so you can recreate the issue. However great update, that will come in handy.
  7. @Richard Jedlička I really like this approach. Where and how do you define your environment variables? Do you have a separate file for this and use the putenv command?
  8. Could you please describe more specific what you are trying to achieve? What you mean by "whitelist"?
  9. Here is another advantage of using composer: I am using an automated deployment process for my clients websites via github actions. Right now I have to put all modules in the modules directory under git control and commit every module update to git. This makes every module update another commit in the git log and the git repository very large. With composer.json I would just update one file and my github action (or buddy, or Vercel or whatever deployment tool you use) would install these dependencies.
  10. I think all modules should be installable via composer as it makes everything more maintainable. There is an composer installer for ProcessWire modules, so you just have to add a composer.json file to your module and the module will be installed in the right directory. Here is a good explanation One advantage of installing modules via compoeser is, that you can version control your composer.json file or have different modules based on your environment:
  11. I have added a request "findRaw should have support for joining parents and references" (and also for getting option field titles) here https://github.com/processwire/processwire-requests/issues/427 @adrian @thetuningspoon
  12. Here is an article where I did something similar for a client project "Disable select option if already selected in another select box". In my case it is only a JavaScript without settings and it works for every select, not only in Pro fields table.
  13. Please read this blog entry. You can use images, links, a dropdown or your own custom solution for adding new matrix items: New Repeater and Repeater Matrix features (processwire.com)
  14. Yoast SEO is a plugin for WordPress. SeoMaestro is a similar module for ProcessWire.
  15. @bernhard I am not using or maintaining this module anymore, so I really don't know if it works. Best way to be sure is to try it out. Sureley Hybrid Auth should be updated to latest version.
  16. I think this should be the default for credentials in ProcessWire. Many other CMS or Frameworks like Laravel or Statamic (which is an Laravel application) use this method.
  17. Use this site, to generate all needed favicons and also the needed HTML code: Favicon Generator for perfect icons on all browsers (realfavicongenerator.net)
  18. Hey @mel47 What you mean by can't see data? Is the grid displayed, but the cells are empty? Is nothing displayed? Do you get Javascript errors in the dev console or maybe PHP errors (turn on debug mode). Can you share the JSON response?
  19. @teppo Would you mind changing the link in the blog post? It is now https://github.com/jmartsch/AnonymizeFields or https://processwire.com/modules/anonymize-fields. I needed to change the name of the repo so I could submit it to ProcessWire's module directory.
  20. Yes, right now it lists all fields and then anonymizes the selected fields on every page, regardless of the template. If more people are interested in this module, I could add more options. You are also free to modify the code or contribute additions to the module @wbmnfktr.
  21. This module allows you to select fields that get anonymized after a defined period of time. Anonymization refers to either replacing field values with a configurable fill word, or removing stored data altogether. The time period after which page content gets anonymized can be configured (default is 60 days), and anonymized fields can be selected manually via module config screen. Behind the scenes LazyCron is used to trigger the anonymization process, which makes the whole process completely automatic. The module was developed for a client that handles job applications. The software we developed required to anonymize personal identifiable data after a specific amount of time, if the applicant did not get the job, according to the law DSGVO. There might be other uses, where this module could come in handy. Thanks @teppo for mentioning it in ProcessWire Weekly #393. I hope you don't mind, that I copied the description from your site? You can find the module at https://github.com/jmartsch/AnonymizeFields and in the modules directory at https://processwire.com/modules/anonymize-fields
  22. I love 💖the aesthetics of the site. Very great work and visually appealing 👁️. There are some performance issues when zooming the map (because there are many retailers shown at once and maps get sluggish with many markers, even with MarkerClusterer), and the find function could be accomplished with a geolocate button (take actual position of you, to find dealers that are near you). Take a look at P. Jentschura – Natürliche Produkte für den Säure-Basen-Haushalt (p-jentschura.com) which as over 5000 dealers, where I tackled the performance problem. Also you could add a "Clear search" or "Reset" button, because If you clicked one dealer it is impossible to go back to the whole list. If you have interest in optimizing the whole map application you can contact me. I did several map applications in the last years. In addition I wrote an "ImportRetailers" module for one of my clients, that geocodes the addresses via geocoder-php/google-maps-provider which uses also caching if you query the same address again (and has almost no request restrictions).
  23. There is also RockTabulator, which is the successor to RockGrid. And most things that you can do with RockFinder are now possible with the ProcessWire 3.0.172 – Find faster and more efficiently. Take a look at the findRaw and findJoin methods.
×
×
  • Create New...