Jump to content

General site settings module


pmarki

Recommended Posts

Please try...

wire('settings')

Note the difference in quotation marks - the forum editor changes single quotes to curly quotes (at least, they look like it to me) Such quotes are not accepted as string markers in PHP, so if you copied-and-pasted directly from Macrura's reply, you would probably get an error like that.

  • Like 3
Link to comment
Share on other sites

  • 5 months later...

Hi,

Help: Echo field label?

echo $settings->as_tel->label; //dont work

or

$module = wire('modules')->get('ProcessGeneralSettings');
echo $field = $module->get('as_tel')->label; //dont work

Thanks

Link to comment
Share on other sites

Hello all.

I was wondering about the use of this module and would like to check for your opinion, guys, before I start testing it. Presently I setup manually a simple page where all my general site settings fields resign (Settings) with  no template assigned on it.

After that I define a variable $settings (could be a name of your preference ) in _init.php

$settings = $pages->get('/settings/'); // Grab the page url and add it here
or 
$settings = $pages->get(settings_page_id); // Grab the page ID and add it here

After that, I am able to print any field value in the markup by using:

echo $settings->fied_name // text and integer value fields
or
echo $settings->some_image_field->first->size(X,Y)->url // Just an example for images etc.

For sure the limit is the API of PW for any field and the parameters with it.

So my wondering is would the use of the module give more functionality as of the present setup? Bear in mind, that for a few clients I already setup the access to Settings page and they can change anything that is there or provide access to somebody else using PW user permissions options.

The Settings page can hold all sorts of PW fields available + custom ones that you've created/added and text and text area has absolutely no issues being multilanguage.

Respect to the mod development team for the time and efforts for sure, I am just trying to figure out the benefits of use over the present setup.

Link to comment
Share on other sites

20 minutes ago, MilenKo said:

So my wondering is would the use of the module give more functionality as of the present setup? Bear in mind, that for a few clients I already setup the access to Settings page and they can change anything that is there or provide access to somebody else using PW user permissions options.

The Settings page can hold all sorts of PW fields available + custom ones that you've created/added and text and text area has absolutely no issues being multilanguage.

Respect to the mod development team for the time and efforts for sure, I am just trying to figure out the benefits of use over the present setup.

i would stick with your regular fields page for editing settings; I don't think this module is maintained; i have a fork of it with a lot of new features and I use it on some sites, but then i made the Settings Factory module, so I use that instead now. You should be aware that the stock module is only accessible to super admin; one of my mods to the module was to create the permissions to enable other users to access settings; also i had to split it into a process module and the module that holds the settings, else settings not accessible to front end etc..

 

Link to comment
Share on other sites

I see Macrura. I would watch closely the development of your mod, however, the options and setups seems sort of way too much for the purpose of my simple projects that hold a logo, few text fields etc. At least I got on the right track using a settings page to hold general variables ;)

Link to comment
Share on other sites

26 minutes ago, MilenKo said:

I see Macrura. I would watch closely the development of your mod, however, the options and setups seems sort of way too much for the purpose of my simple projects that hold a logo, few text fields etc. At least I got on the right track using a settings page to hold general variables ;)

yes, if you need to hold those sorts of things, especially images, you should stick with real fields.

The main advantages of using a settings module could be summed up as:

(1) fast an easy to add a settings page (since you can reuse the same json file) and don't need to setup fields
(2) dedicated edit screen with no tabs as on the edit screen (no children, settings etc), no delete
(3) settings stored as JSON in 1 table/field (module config)
(4) human readable editing url, no url param
(5) since it is a process module, easy to link to the settings page directly in the admin menus

more discussions on the Settings Factory topic..
 

  • Like 2
Link to comment
Share on other sites

9 minutes ago, adrian said:

I haven't used this module, but I have used @Macrura's Settings Factory which is awesome. Is there any reason to consider this module over Settings Factory? Genuine question because I don't know what the differences are :)

@adrian  do you have a link for this module? I searched " Settings Factory " in the modules section and it returned zero results.

I am curious to check it out

thank you

Link to comment
Share on other sites

54 minutes ago, adrian said:

I haven't used this module, but I have used @Macrura's Settings Factory which is awesome. Is there any reason to consider this module over Settings Factory? Genuine question because I don't know what the differences are :)

Objectively, this module provides a clever interface for adding fields to your settings. My fork of it supported more fields, and other improvements. The warning here, as is mentioned earlier in this thread is that you do not want to install this module if you use Lister Pro, there is a serious incompatibility that causes your Lister Pro listers to lose their settings.

Besides that, Settings Factory allows multiple settings pages (unlimited) that you can link to in your admin menus; this module would be a single settings screen only. Further, you must use the fork if you want to have the settings be accessible to non-Superusers.

  • Like 1
Link to comment
Share on other sites

3 minutes ago, Macrura said:

you do not want to install this module if you use Lister Pro, there is a serious incompatibility that causes your Lister Pro listers to lose their settings.

Just to clarify - is it just this module, or also Settings Factory that has this issue?

If it's just this module then I can't see a reason to promote/maintain this module anymore. Am I missing something?

Link to comment
Share on other sites

30 minutes ago, adrian said:

Just to clarify - is it just this module, or also Settings Factory that has this issue?

My module (Settings Factory) has no relation to this module (General Settings), it doesn't share or inherit any code. Settings Factory does not set a global var for the settings (that is left to the user and how they interact with the SF api), therefore it does not suffer from the same issue which is that this module by default/upon installation sets a global $wire var for $settings, which is already being used by LP.

33 minutes ago, adrian said:

If it's just this module then I can't see a reason to promote/maintain this module anymore. Am I missing something?

I don't personally endorse or promote, or recommend this module – i advise that it NOT be used until the $settings problem is fixed; as i stated in earlier posts, i used it on a couple of sites, forked it and fixed all the issues, but for the last 10 months i only use Settings Factory and i don't use this module at all. It is fine with me if this module is deprecated.

  • Like 2
Link to comment
Share on other sites

5 minutes ago, Macrura said:

sets a global $wire var for $settings, which is already being used by LP

Thanks for the explanation on this (apparently I didn't read above). 

I must admit that I think LP shouldn't use $settings - it should be more specific, like $listerProSettings or similar.

I actually defined a global $wire var $settings for use with Settings Factory on one of my current projects - time to change that I guess :)

Link to comment
Share on other sites

so one of the first things i did was change the global to g_settings

https://github.com/outflux3/ProcessGeneralSettings/blob/master/GeneralSettings.module#L31

besides that i added support for placeholders, collapsed states, markup, import/export of settings..

15 minutes ago, adrian said:

I must admit that I think LP shouldn't use $settings - it should be more specific, like $listerProSettings or similar.

+1, i'm super paranoid about global vars now, since i lost all of the listers on one site... not sure if this problem still exists, i may have posted an issue report on the LP thread and Ryan may have changed it, haven't checked though...\

17 minutes ago, adrian said:

I actually defined a global $wire var $settings for use with Settings Factory on one of my current projects - time to change that I guess :)

did you encounter any problems with LP? i usually use more verbose globals for that, but on the other hand i have a new module that uses a $meta global, and another one with $theme; sometimes it's nice for the globals to be concise

  • Like 3
Link to comment
Share on other sites

  • 4 weeks later...

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By Robin S
      This module lets you add some custom menu items to the main admin menu, and you can set the dropdown links dynamically in a hook if needed.
      Sidenote: the module config uses some repeatable/sortable rows for the child link settings, similar to the ProFields Table interface. The data gets saved as JSON in a hidden textarea field. Might be interesting to other module developers?
      Custom Admin Menus
      Adds up to three custom menu items with optional dropdowns to the main admin menu.
      The menu items can link to admin pages, front-end pages, or pages on external websites.
      The links can be set to open in a new browser tab, and child links in the dropdown can be given an icon.
      Requires ProcessWire v3.0.178 or newer.
      Screenshots
      Example of menu items

      Module config for the menus

      Link list shown when parent menu item is not given a URL

      Advanced
      Setting child menu items dynamically
      If needed you can set the child menu items dynamically using a hook.
      Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $colours = $event->wire()->pages->findRaw('template=colour', ['title', 'url', 'page_icon']); $children = []; foreach($colours as $colour) { // Each child item should be an array with the following keys $children[] = [ 'icon' => $colour['page_icon'], 'label' => $colour['title'], 'url' => $colour['url'], 'newtab' => false, ]; } $event->return = $children; } }); Create multiple levels of flyout menus
      It's also possible to create multiple levels of flyout submenus using a hook.

      For each level a submenu can be defined in a "children" item. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); if($menu_number === 1) { $children = [ [ 'icon' => 'adjust', 'label' => 'One', 'url' => '/one/', 'newtab' => false, ], [ 'icon' => 'anchor', 'label' => 'Two', 'url' => '/two/', 'newtab' => false, 'children' => [ [ 'icon' => 'child', 'label' => 'Red', 'url' => '/red/', 'newtab' => false, ], [ 'icon' => 'bullhorn', 'label' => 'Green', 'url' => '/green/', 'newtab' => false, 'children' => [ [ 'icon' => 'wifi', 'label' => 'Small', 'url' => '/small/', 'newtab' => true, ], [ 'icon' => 'codepen', 'label' => 'Medium', 'url' => '/medium/', 'newtab' => false, ], [ 'icon' => 'cogs', 'label' => 'Large', 'url' => '/large/', 'newtab' => false, ], ] ], [ 'icon' => 'futbol-o', 'label' => 'Blue', 'url' => '/blue/', 'newtab' => true, ], ] ], [ 'icon' => 'hand-o-left', 'label' => 'Three', 'url' => '/three/', 'newtab' => false, ], ]; $event->return = $children; } }); Showing/hiding menus according to user role
      You can determine which menu items can be seen by a role by checking the user's role in the hook.
      For example, if a user has or lacks a role you could include different child menu items in the hook return value. Or if you want to conditionally hide a custom menu altogether you can set the return value to false. Example:
      $wire->addHookAfter('CustomAdminMenus::getMenuChildren', function(HookEvent $event) { // The menu number is the first argument $menu_number = $event->arguments(0); $user = $event->wire()->user; // For custom menu number 1... if($menu_number === 1) { // ...if user does not have some particular role... if(!$user->hasRole('foo')) { // ...do not show the menu $event->return = false; } } });  
      https://github.com/Toutouwai/CustomAdminMenus
      https://processwire.com/modules/custom-admin-menus/
    • By tcnet
      This module for ProcessWire sends a notification email for each failed login attempt. Similar modules exists already in the module directory of ProcessWire. However, this module is designed to notify, even if specified user doesn't exist.
      Settings
      The settings for this module are located in the menu Modules=>Configure=>LoginFailNotifier.
      Notification email
      Specifies the email address to which the notification emails should be sent.
        Email subject
      Specifies the subject line for the notification email.
        Post variables
      Specifies the $_POST variables to be included in the notification email. Each variable must be separated by a comma. For example: login_name,login_pass
        Server variables
      Specifies the $_SERVER variables to be included in the notification email. Each variable must be separated by a comma. For example: REMOTE_ADDR,HTTP_USER_AGENT
      Link to ProcessWire module directory:
      https://processwire.com/modules/login-fail-notifier/
      Link to github.com:
      https://github.com/techcnet/LoginFailNotifier
    • By Fokke
      ProcessWire 3.x markup module for rendering meta tags in HTML document head section. Note that this module is not a full-blown SEO solution, but rather a simple tool for rendering meta tags based on module configuration. Adding custom meta tags is also supported.
      Built-in meta tags
      The following meta tags are supported out-of-the-box:
      Document title consisting of page title and site name Character set Canonical Viewport Description Keywords Hreflang tags Open Graph og:title og:site_name og:type og:url og:description og:image og:image:width og:image:height Twitter meta tags twitter:card twitter:site twitter:creator twitter:title twitter:description twitter:image Facebook meta tags fb:app_id The full documentation with configurable options can be found here: https://github.com/Fokke-/MarkupMetadata
       
      Requirements:
      ProcessWire>=3.0.0 PHP >=7.1 Installation using Composer
      composer require fokke/markup-metadata Manual installation
      Download latest version from https://github.com/Fokke-/MarkupMetadata/archive/master.zip Extract module files to site/modules/MarkupMetadata directory.
    • By m.sieber
      ITRK-Service for ProcessWire
      Module for the automated transfer of imprint, data protection declaration and terms and conditions from IT-Recht Kanzlei to your ProcessWire installation
      What is ITRK Service for ProcessWire?
      ITRK-Service for ProcessWire is a free module for ProcessWire CMS. It provides an interface to the update service of IT-Recht Kanzlei, via which the legal texts of your online presence are automatically updated. In this way, the texts remain legally secure and warning-proof in the long term. Imprint, data protection declaration, revocation and general terms and conditions are currently supported.
      You can find our documentation (in german language) here: https://www.pupit.de/itrk-service-for-processwire/dokumentation/

      Download: https://www.pupit.de/itrk-service-for-processwire/
      Github: https://github.com/pupit-de/pwItrkServiceConnector
    • By LuisM
      Symprowire is a PHP MVC Framework based and built on Symfony using ProcessWire 3.x as DBAL and Service-Provider
      It acts as a Drop-In Replacement Module to handle the Request/Response outside the ProcessWire Admin. Even tough Symfony or any other mature MVC Framework could be intimidating at first, Symprowire tries to abstract Configuration and Symfony Internals away as much as possible to give you a quick start and lift the heavy work for you.
      The main Goal is to give an easy path to follow an MVC Approach during development with ProcessWire and open up the available eco-system.
      You can find the GitHub Repo and more Information here: https://github.com/Luis85/symprowire
      Documentation
      The Symprowire Wiki https://github.com/Luis85/symprowire/wiki How to create a simple Blog with Symprowire https://github.com/Luis85/symprowire/wiki/Symprowire-Blog-Tutorial Last Update
      16.07.2021 // RC 1 v0.6.0 centralized ProcessWire access trough out the Application by wrapping to a Service https://github.com/Luis85/symprowire/releases/tag/v0.6.0-rc-1 Requirements
      PHP ^7.4 Fresh ProcessWire ^3.0.181 with a Blank Profile Composer 2 (v1 should work, not recommended) The usual Symfony Requirements Features
      Twig Dependency Injection Monolog for Symprowire Support for .env YAML Configuration Symfony Console and Console Commands Symfony Webprofiler Full ProcessWire access inside your Controller and Services Webpack Encore support Caveats
      Symfony is no small Framework and will come with a price in terms of Memory Usage and added Overhead. To give you a taste I installed Tracy Debugger alongside to compare ProcessWire profiling with the included Symfony Webprofiler

      So in a fresh install Symprowire would atleast add another 2MB of Memory usage and around 40ms in response time, should be less in production due to the added overhead of the Webprofiler in dev env
       
×
×
  • Create New...