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 MarkE
      This fieldtype and inputfield bundle was built for storing measurement values within a field, rendering them in a variety of formats and converting them to other units or otherwise modifying them via the API.
      The API consists of a number of predefined functions, some of which include...
      render() for rendering the measurement object, valueAs() for converting the value to another unit value, convertTo() for converting the whole measurement object to different units, and add() and subtract() for for modifying the stored value by the value (converted as required) in another measurement. In the admin the inputfield includes a checkbox (which can be optionally disabled) for converting values on page save. For an example if a value was typed in as centimeters, the unit was changed to metres, and the page saved with this checkbox selected, said value would be automatically converted so that e.g. 170 cm becomes 1.7 m.

      A simple length field using Fieldtype Measurement and Inputfield Measurement.
      Combination units (e.g. feet and inches) are also supported.
      Please note that this module is 'proof of concept' at the moment - there are limited units available and quite a lot of code tidying to do. More units will be added shortly.
      See the GitHub at https://github.com/MetaTunes/FieldtypeMeasurement for full details and updates.
    • By tcnet
      File Manager for ProcessWire is a module to manager files and folders from the CMS backend. It supports creating, deleting, renaming, packing, unpacking, uploading, downloading and editing of files and folders. The integrated code editor ACE supports highlighting of all common programming languages.
      https://github.com/techcnet/ProcessFileManager

      Warning
      This module is probably the most powerful module. You might destroy your processwire installation if you don't exactly know what you doing. Be careful and use it at your own risk!
      ACE code editor
      This module uses ACE code editor available from: https://github.com/ajaxorg/ace

      Dragscroll
      This module uses the JavaScript dragscroll available from: http://github.com/asvd/dragscroll. Dragscroll adds the ability to drag the table horizontally with the mouse pointer.
      PHP File Manager
      This module uses a modified version of PHP File Manager available from: https://github.com/alexantr/filemanager
       
    • By tcnet
      This module implements the website live chat service from tawk.to. Actually the module doesn't have to do much. It just need to inserted a few lines of JavaScript just before the closing body tag </body> on each side. However, the module offers additional options to display the widget only on certain pages.
      Create an account
      Visit https://www.tawk.to and create an account. It's free! At some point you will reach a page where you can copy the required JavaScript-code.

      Open the module settings and paste the JavaScript-code into the field as shown below. Click "Submit" and that's all.

      Open the module settings
      The settings for this module are located int the menu Modules=>Configure=>LiveChatTawkTo.

       
    • By tcnet
      Session Viewer is a module for ProcessWire to list session files and display session data. This module is helpful to display the session data of a specific session or to kick out a logged in user by simply delete his session file. After installation the module is available in the Setup menu.

      The following conditions must be met for the module to work properly:
      Session files
      Session data must be stored in session files, which is the default way in ProcessWire. Sessions stored in the database are not supported by this module. The path to the directory where the session files are stored must be declared in the ProcessWire configuration which is by default: site/assets/sessions.
      Serialize handler
      In order to transform session data easier back to a PHP array, the session data is stored serialized. PHP offers a way to declare a custom serialize handler. This module supports only the default serialize handlers: php, php_binary and php_serialize. WDDX was dropped in PHP 7.4.0 and is therefore not supported by this module as well as any other custom serialize handler. Which serialize handler is actually used you can find out in the module configuration which is available under Modules=>Configure=>SessionViewer.

      Session data
      The session data can be displayed in two different ways. PHP's default output for arrays print_r() or by default for this module nice_r() offered on github: https://github.com/uuf6429/nice_r. There is a setting in the module configuration if someone prefers print_r(). Apart from the better handling and overview of the folded session data the output of nice_r() looks indeed nicer.

      Links
      ProcessWire module directory
      github.com
    • By Robin S
      Repeater Easy Sort
      Adds a compact "easy-sort" mode to Repeater and Repeater Matrix, making those fields easier to sort when there are a large number of items.
      The module also enhances Repeater Matrix by allowing a colour to be set for each matrix type. This colour is used in the item headers and in the "add new" links, to help visually distinguish different matrix types in the inputfield.
      Screencasts
      A Repeater field

      A Repeater Matrix field with custom header colours

      Easy-sort mode
      Each Repeater/Matrix item gets an double-arrow icon in the item header. Click this icon to enter easy-sort mode.
      While in easy-sort mode:
      The items will reduce in width so that more items can be shown on the screen at once. The minimum width is configurable in the field settings. Any items that were in an open state are collapsed, but when you exit easy-sort mode the previously open items will be reopened. You can drag an item left/right/up/down to sort it within the items. The item that you clicked the icon for is shown with a black background. This makes it easier to find the item you want to move in easy-sort mode. You can click an item header to open the item. An "Exit easy-sort mode" button appears at the bottom of the inputfield. Configuration
      In the field settings for Repeater and Repeater Matrix fields you can define a minimum width in pixels for items in easy-sort mode. While in easy-sort mode the items will be sized to neatly fill the available width on any screen size but will never be narrower than the width you set here.
      In the field settings for Repeater Matrix you can define a custom header colour for each matrix type using an HTML "color" type input. The default colour for this type of input is black, so when black is selected in the input it means that no custom colour will be applied to the header.
      Exclusions
      The easy-sort mode is only possible on Repeater/Matrix fields that do not use the "item depth" option.
       
      https://github.com/Toutouwai/RepeaterEasySort
      https://processwire.com/modules/repeater-easy-sort/
×
×
  • Create New...