Posts by DMedia

    In der Dokumentation wird (vielleicht übersehe ich es) nirgends erwähnt, dass die damit aktualisiert werden können, wenn sie bereits gecached sind. Stattdessen schlagen sie das Testen der aktualisierten Vorschau mittels bitly Links vor, was sie sonst nicht tun müssten:

    Troubleshooting Cards
    developer.twitter.com

    Wenn es natürlich funktioniert ist das gut, ändert aber nichts daran, dass es keine konkrete API dafür gibt.

    Facebook aktualisiert die Vorschau laut Dokumentation alle 30 Tage nach dem ersten Auslesen automatisch, lässt aber durchgehend eine manuelle Aktualisierung mittels Debugger oder API zu. Twitter aktualisiert die Vorschau für die "Twitter-Cards" dagegen ungefähr alle 7 Tage, was aber auch nicht manuell angestoßen werden kann.


    Verwenden von Objekten - Teilen - Dokumentation - Facebook for Developers

    Getting started with Cards
    developer.twitter.com


    Wenn ich das auf Anhieb richtig sehe, könnte man mittels Plugin bei der zeitgesteuerten Veröffentlichung eines Artikels im WSC zumindest für Facebook automatisch eine Aktualisierung veranlassen, wenn man sich per EventListener im dazugehörigen Cronjob einhängt. Der Request erfordert jedoch eine Authentifizierung des Seitenbetreibers.

    Der Medienanbieter für Videos von der Tagesschau könnte wie folgt aussehen:


    Medienanbieter

    Tagesschau


    Regulärer Ausdruck

    https?://(www\.)?tagesschau\.de/multimedia/video/video-(?P<ID>\d+)\.html


    HTML-Code

    HTML
    <div class="messageVideoContainer">
        <iframe src="https://www.tagesschau.de/multimedia/video/video-{$ID}~player.html" width="512" height="288" allowfullscreen frameBorder="0" scrolling="no"></iframe>
    </div>


    Anschließend kann ein Video wie bspw. https://www.tagesschau.de/multimedia/video/video-914583.html einfach über die URL eingebunden werden. Das funktioniert dann zwar nicht mit Videos, deren URL einen eigenen Titel erhält, aber dort kann man sich über den Teilen-Button die benötigte Video-URL holen.

    Für die Einbindung von YouTube Videos müssen die Videolinks lediglich in einem separaten Absatz als Text eingefügt werden, wenn der entsprechende Medienanbieter im ACP unter Inhalt > BBCodes > Medienanbieter aktiviert ist. Das ist bei YouTube standardmäßig der Fall.


    Ist die URL bei dir im Beitrag eventuell ein Link? Wenn ja, dann entferne mal die Verlinkung.


    Für Videos von der Tagesschau kann man anschließend einen separaten Medienanbieter anlegen. Hast du dafür mal ein Beispiel Video?

    Just to close up on this: Exactly as I suspected, the error was caused by the fact that the option to declare the group application as a mandatory field was enabled (last option), but no group was actually set to be visible/selectable during registration. This will be fixed with the next plugin update.


    The problem would (most-likely) not have occurred if the following settings I suggested had been made for at least one user group:

    Der selbe Fehler tritt unter WSC 5.3.13 auch im Ticketsystem von Darkwood.Design beim TicketAdd Formular auf.

    Requested URL
    GET /support/ticket-add/
    Referrer
    https://<redacted>/support/
    Error Message
    Undefined index: 3d43f83f21bf57577a500f1dc7ab075437aafd1d
    Type
    wcf\system\exception\ErrorException
    File (Line)
    /var/www/<redacted>/html/lib/system/WCF.class.php (349)
    Stacktrace
    1. /var/www/<redacted>/html/templates/compiled/4_wcf_2___formContainer.php (52): wcf\system\WCF::handleError(…)
    2. /var/www/<redacted>/html/lib/system/template/TemplateEngine.class.php (334): include(…)
    3. /var/www/<redacted>/html/lib/system/template/TemplateEngine.class.php (562): wcf\system\template\TemplateEngine->display(…)
    4. /var/www/<redacted>/html/lib/system/form/builder/container/FormContainer.class.php (58): wcf\system\template\TemplateEngine->fetch(…)
    5. /var/www/<redacted>/html/templates/compiled/4_wcf_2___form.php (94): wcf\system\form\builder\container\FormContainer->getHtml(…)
    6. /var/www/<redacted>/html/lib/system/template/TemplateEngine.class.php (334): include(…)
    7. /var/www/<redacted>/html/lib/system/template/TemplateEngine.class.php (562): wcf\system\template\TemplateEngine->display(…)
    8. /var/www/<redacted>/html/lib/system/form/builder/FormDocument.class.php (416): wcf\system\template\TemplateEngine->fetch(…)
    9. /var/www/<redacted>/html/templates/compiled/4_ticketsystem_2_ticketAdd.php (1903): wcf\system\form\builder\FormDocument->getHtml(…)
    10. /var/www/<redacted>/html/lib/system/template/TemplateEngine.class.php (334): include(…)
    11. /var/www/<redacted>/html/lib/page/AbstractPage.class.php (323): wcf\system\template\TemplateEngine->display(…)
    12. /var/www/<redacted>/html/lib/page/AbstractPage.class.php (114): wcf\page\AbstractPage->show(…)
    13. /var/www/<redacted>/html/lib/system/request/Request.class.php (83): wcf\page\AbstractPage->__run(…)
    14. /var/www/<redacted>/html/lib/system/request/RequestHandler.class.php (107): wcf\system\request\Request->execute(…)
    15. /var/www/<redacted>/html/support/index.php (10): wcf\system\request\RequestHandler->handle(…)

    Nun habe ich aber übershen, dass "moderiert" bedeutet, dass deren beiträge dann extra freigeschaltet werden müssen??

    Der Typ "moderiert" bedeutet nur, dass sich Mitglieder für die Gruppe bewerben können. Wenn die Benutzergruppe die Berechtigung hat, Beiträge ohne Moderation (Prüfung eines Moderators) zu erstellen, müssen Beiträge auch nicht freigeschaltet werden. Die beiden Begriffe stehen hierbei nicht in einem Kontext.

    Where do I find this particular setting in the ACP?

    You can find the option(s) by selecting a group under Users > User Groups. Please also add a checkmark to the option that shows the group during registration. It should be below the text field for the group leader. I have the suspision that the plugin is indeed responsible for the error as it may not handle registration forms correctly if no user group is set to be selectable but the option that its mandatory/required is enabled. If you have correctly setup a user group, it should be visible in the registration form.

    So it looks as though this Plugin is not going to work for me.

    You can probably make it work for you just fine. What you want is setting the group type for the groups users should be able to join to "free for all" so you don't have to confirm the application after registration. There is no reason to give up that fast :)


    The problem is that you essentially have two plugins installed what i think is what you're not aware of.


    The first one is "WoltLab Suite Core: Moderated User Groups" which adds the functionality of user group applications (via user control panel). This plugin is included in your license.


    By default, you can not add group applications to the registration form. This functionality comes from the following plugin:


    As this is a plugin from a third-party developer, you can only get support from them. It's often stated somewhere in the description. In this case, you would need to ask Marcel Beckers in his support forum over at YoureCom.de. If there really is an issue with the plugin, he is able to do something about it.


    Honestly, I still think it's just a configuration error as other people using custom profile fields would have already reported this. Thats why I asked you to take a screenshot of the error message, which also shows the entire registration form.

    In the ACP> "Pages" (where these plugins appear), I am unable to delete anything to do with Moderated User Groups, etc.,

    as the option to delete (the "X" for delete is not active)

    ACP > Pages is a list of available pages in your installation. If a plugin adds a page, it gets added to this list. If you want to uninstall a plugin and everything that comes with it, you need to remove it under Configuration > Packages.

    The custom profile field has (almost guaranteed) nothing to do with the registration not working when group applications are enabled during registration. Can you take a screenshot of the error message showing the entire registration form?


    Also, have you set the user group type of the groups you want people to be able to join to something other than "Closed" (free for all in your case)?

    Addition: The plugin "Usergroups application during registration" adds an option to show the group during registration. Did you set this accordingly?


    Edit:

    Adding group applications to the registration form does not seem to be part of WoltLab's plugin for moderated user groups. You may want to post your question over at YoureCom so Marcel Beckers can have a look at this. I have not encountered this plugin once and really thought this would be possible by default :D

    Obvious;y, because of the Custom User Field I have implemented on the "registration form", this plugin cannot function properly.

    This is not quite "obvious", because the plugin does not interfere with custom profile fields during registration at all and since you have disabled group applications during the registration, the issue is most-likely not caused by simply installing the plugin.


    It seems you still have the plugin installed and i was able to register just fine?


    I've marked my account for deletion (7 days), but if you don't have the plugin installed, please do so and delete the account, so i can try again immediately.

    Das scheint nicht korrekt zu sein. Das entsprechende Cookie wurde bei mir am 17. Juli, also dem Zeitpunkt des Updates, gesetzt, und läuft am 20. Dezember ab. Das sind etwas mehr als 14 Tage. ;)

    Bist du ein Gast, so bekommst du eine Session-ID zugewiesen. Diese wird nach 2 Stunden Inaktivität vom Server gelöscht, danach existiert zwar weiterhin der Cookie im Browser, der Server kann damit aber nichts mehr anfangen und vergibt bei einem erneuten Besuch eine neue Session-ID.


    Als angemeldeter Benutzer bleibt die Session auf dem Server für 14 Tage bestehen, bevor diese verworfen wird. Ruft man die Seite innerhalb dieses Zeitraums erneut auf, verlängert sich die Session wieder um 14 Tage. Das entspricht dem "angemeldet bleiben".

    ;)

    Please notice that the significant change I made this time was changing "text" TO "password".

    I don't think this change was necessary at all, but since the field is only relevant for registration, it probably doesn't matter.

    Do you believe this change has finally corrected every setting so that individuals registering will fill out the Registration Form as REQUIRED


    with NO more problems?

    At first glance, there doesn't seem to be any other problems :thumbup:

    >deleting ^Accept$ in BOTH Custom User Fields (one for the Adult Acceptance and Age Verification), and the other Custom User Field (for the Birthday Entry)

    The RegEx should have never been set in the birthday profile field. That's why i wanted to see its settings before. It explains why this field was throwing an unusual error during registration. The RegEx should only be set in the custom text profile field where you want to require the word 'Accept'. With your current settings, users can enter anything they want and you have to manually approve it. You will have less work activating and communicating with new users by just getting the RegEx to work. Only add it to your acceptance profile field.


    Also, you should still set both profile fields to be editable by "Owner during registration and Administrator" as this had probably nothing to do with the issues preventing you from submitting the registration form and prevents users from changing the fields value afterwards.

    I currently have no idea what could be the issue here without looking at it myself (DM me if you are willing to provide me with a temporary admin login). You may have to go through it again, one at a time. First try to disable your age verification profile field (remove checkmark on overview) to check if the minimum age requirement / birthday profile field works as intended. If it doesn't work, please provide screenshots of its settings, but if it does work on its own, maybe its an issue that must be resolved by creating a ticket.

    First of all, your profile field is still set to be editable by the owner (user) at any given time which enables the user to change it after registration. Also, the profile field is currently visible for everyone, but since everyone has to fill it out and its value never changes anyway, you may want to make it visible only to the owner and administrators so as not to display unnecessary information on user profiles. I would recommend the following settings:



    However, this field (even with your settings) works fine in my environment and I don't see any issues with your setup right away. What is interesting to me is that the birthday field also throws a generic error. If the date is below the minimum age, a corresponding error would be displayed instead. What do the settings for this profile field look like?


    Also, without knowing too much about US law, isn't it enough to set a minimum age that users automatically confirm when they register?

    Custom User Fields does not provide for this.

    This is not true. If you check the options "Owner must provide a valid value" (e.g. in combination with a regex shown by Black Rider ) and "Field will be visible during registration" when creating a custom profile field, it will be required during/for registration.

    but later deleting that he/she ever committed to such a statement of "acceptance"

    You can make a custom profile field editable by "Owner during registration and Administrator" which will prevent users from changing its value afterwards.

    age verification" of at least 18 Years of Age

    You can set a minimum age under Configuration > Users > Registration which automatically adds the birthday profile field to the registration form. You can then set this profile field to be editable by "Owner during registration and Administrators" and users will not be able to change their birthday after registration.