Jump to content

AndZyk

Members
  • Posts

    645
  • Joined

  • Days Won

    8

Posts posted by AndZyk

  1. 15 minutes ago, Frank Schneider said:

    Danke das hat funktioniert, der Zähler der Authlogs ändert sich nicht ist das Normal?

    Freut mich zu hören, dass es funktioniert hat.

    Ohne mehr Informationen, kann ich leider nichts zu dem Zähler sagen.

    Ist der Zähler ein Feld vom Typ Nummer in einem Template?
    Ist der Zähler die Gesamtzahl aller Seiten mit dem Template „Authlogs“?
    Die Seiten mit dem Template „Authlogs“ sollten im Papierkorb sein und je nach Selector, können diese immer noch gefunden und für eine Gesamtzahl dazu gezählt werden.

  2. Hallo @Frank Schneider,

    du könntest die Seiten per API $pages->delete() löschen:

    // Alle Seiten mit dem Template authlogs nacheinander
    $authlogs = $pages->find('template=authlogs');
    
    foreach ($authologs as $authlogPage) {
        $pages->delete($authlogPage);
    }
    
    // Alle Seiten der Elternseite mit dem Titel Authlogs rekursiv
    $authlogsParent = $pages->get("title=Authlogs");
    $pages->delete($authlogsParent, true);

    Einfach irgendwo in einem Template einfügen und die Seite mit dem Template aufrufen.

    Ansonsten können glaube ich Module wie der ListerPro oder Batch Child Editor Stappelbearbeitung von Seiten.

    Gruß, Andreas

  3. Hi @Boost,

    I don't have much experience with the new TinyMCE yet, but I couldn't find a way to rename classes of the default styles.

    But you can hide the default styles and add your own classes:

    #Align { display: none }
    #UIkit .uk-text-left { text-align: left } /* Text Left */
    #UIkit .uk-text-center { text-align: center } /* Text Center */
    #UIkit .uk-text-right { text-align: right } /* Text Right */

    Source: https://processwire.com/blog/posts/using-tinymce-6-in-processwire/#specifying-element.class-versus-just-class

    Regards, Andreas

  4. Hello,

    the last few weeks there were four new versions of ProcessWire on the master branch (3.0.226 - 3.0.229) and there seems to be the next one around the corner.
    I like to upgrade all my ProcessWire websites whenever a new master version is released. Currently I am upgrading around 50 websites, which takes a few hours for all of them.

    I have skipped a few of the master releases, but was wondering if it would be possible to provide an module for auto upgrades?
    I know that there is a certain risk involved with auto upgrades and it would not work for the .htaccess file, because this file has its own rules.
    But upgrading the wire folder and the index.php is usually unproblematic, so those could be auto upgraded.

    WordPress for example has auto upgrades enabled for patch versions (x.x.1 to x.x.2) if there is not Git present.
    Currently ProcessWire has no minor versions (x.1.x) and only patch versions (x.x.1), but maybe one could configure in the module settings which branch (dev or master) should be auto upgraded.

    Maybe this could be a setting in the ProcessWire Upgrade module or an extension: https://processwire.com/modules/process-wire-upgrade/
    After the upgrade you could get an email, that your ProcessWire has been upgraded (similar to the Workflow in WordPress).

    There could also be an option for auto upgrading modules. (for example Tracy Debugger 😅)

    What do you think? Is there some major issue speaking against the option for auto upgrades?

    Regards, Andreas

    • Like 1
  5. Hi @Boost,

    you have to add the attribute "uk-lightbox" on a container and then add a link to open the lightbox:

    <!-- Video as link -->
    <div uk-lightbox>
    	<a class="uk-position-cover uk-cover-container" href="<?= $page->block->video_upload->url ?>" data-caption="Caption for the Video">
    		<video src="<?= $page->block->video_upload->url ?>" loop muted playsinline uk-video="autoplay: inview"></video>
    	</a>
    </div>
    
    <!-- Link over video  -->
    <div uk-lightbox>
    	<video src="<?= $page->block->video_upload->url ?>" loop muted playsinline uk-video="autoplay: inview"></video>
    	<a class="uk-position-cover" href="<?= $page->block->video_upload->url ?>" aria-label="Video-Link" data-caption="Caption for the Video"></a>
    </div>

    Regards, Andreas

    • Like 1
  6. Hello @Flashmaster82,

    if you think you found an error:

    1. Look in the console of your developer tools if there is an error.
    2. Try to reproduce the problem on a clean ProcessWire installation.
    3. If you can reproduce it, report it on GitHub (https://github.com/processwire/processwire-issues/) with more insights.

    For me the jQuery date picker is working. So maybe there is an issue on your installation maybe with a conflicting module or caching.

    Regards, Andreas

  7. 5 hours ago, Stefanowitsch said:

    So in order to make the file download working it seems you always have to make a "global file download list" field on a separate page (maybe a "settings" or "downloads" page) and first upload the file there. Then you can chose that file from the textfield. 

    That is what I am doing. I usually add a file field "downloadsForTextareas", which is collapsed if empty by default, to the bottom of the template.

    5 hours ago, Stefanowitsch said:

    If you want to link to a file you should be able to upload the file directly in the popup window instead of selecting "chose file from page".

    That would be nice but works only for images as far as I know, and I have not really used this option yet. I would be nice, if one could set a preferred file field for downloads in the field settings. 👍

    • Like 2
  8. 3 minutes ago, bernhard said:

    I don't like this statement either. ProcessWire is a timeless tool and does care a lot about long time support. That's something great! We should not blame anybody for not being on the latest and greatest versions. But we should make clear, that this is not the recommendation and it's everybodies own decision.

    That was just my attempt of being funny. I thought the smiley would make it clear, but of course I don't want to blame or disrespect anybody. 😉

    If you have reasons to use a PHP version, which had its end of life 4 years and 5 month ago, this is fine. Like you said it is your own decision.

    • Like 1
  9. 37 minutes ago, szabesz said:

    In a perfect life, yes. But is it perfect? 🙂 Jokes aside, as PHP development has been speeding up recently, I do not think it is realistic to expect Ryan and module developers to keep up with that pace. 

    My wording "required" wasn't good. Looking at competitors I think it should be maybe:

    Minimum PHP 7.2 or PHP 7.4. Recommended PHP 8.

    If you still use PHP 5 in 2023 I think you should search help. 😊

    10 minutes ago, cwsoft said:

    Hope this makes things more clear. There is always a chance for getting things wrong in forums, especially if you have to write in languages other than your first language. 

    Thank you for making things clear. I understood your first sentence exactly, that you had experienced those issues with PW, which is not my experience at all.

    I also think that GitHub branches in general should try to target no warning/errors or blank pages. Regarding PW that is already the case in my opinion. 

    • Like 2
  10. 4 hours ago, cwsoft said:

    Even if you don‘t set/increase PW minimum required PHP version, the PW Github dev branch should be running PHP 7.x up to latest PHP 8.2.x at least without throwing warnings or even worse errors or a white page of death.

    I think this is an unfair statement. In my experience PW had no warnings or errors with PHP 8.1 since PW 3.0.210. And for compatibility with PHP 8.2 there is a GitHub issue where you can report warnings or errors: https://github.com/processwire/processwire-issues/issues/1664

    So if you @cwsoft really have experienced a warning, error or "blank page of death", could you please provide an example or report it to this thread? 😉

    Since PHP 8.2 is the latest version and PW has a big core, I think it is fair not to expect it to be compatible with it over night.

     

    Requirements

    In my opinion I think the minimum recommended PHP version should be the last supported PHP version: https://www.php.net/supported-versions.php
    So at the moment this would be PHP 8.0. Recommending an unsupported PHP version maybe would not make a good first impression.

    Versioning

    In my opinion I also would recommend switching the versioning of PW. PW 3.0.xxx started in 2015 and while I understand the explanation for the versioning process, from a marketing and user perspective there is lack of distinction between the different versions. Other CMS celebrate major upgrades with a major version bump (3.1 or 4.0) and some give those versions even silly names just to make it clear in the marketing or for the users, that this version has something special to offer. 😀

     

    But as always, much love for PW. ❤️

    • Like 3
×
×
  • Create New...