Jump to content

Recommended Posts

Hi @kixe or others who might be able to help me out,

I cannot seem to figure out something, I hope you can help. The children Pages – which need auto generated page names – have a Page Reference field called set_part_image. I would like its Title to be part of the name, like this (contrary to its name, it is NOT an image field!): 
date(Y-m-d_H-i-s) set_part_image.title

Meaning I need a time stamp like string followed by the title of that Page field. While this one works:
date(Y-m-d_H-i-s) set_part_image
generating something like: 2017-07-30_11-24-35-1053 where 1053 is the ID of the Page referenced by the field (of course), when using set_part_image.title the name is set to be untitled.

I also get the warning message: 
SetupPageName expects value in field 'set_part_image.title' to autogenerate Pagename

set_part_image.title DOES have a value filled in, so it should not be a problem for the module to get it.

I am using ProcessSetupPageName 2.0.8, BTW.

What am I doing wrong? Any Ideas? Thanks in advance!

Share this post


Link to post
Share on other sites

@szabesz I'm using a page reference field "countries.title"on name format for children without problem. What is your page field value type? I have it on "Single page Page or boolean false when none selected". Have you tried with ONLY set_part_image.title on the name format to see if it works? Make sure that you're using the template's Name format for children and NOT the Automatic Page Name Format of a Page Table.

  • Like 3

Share this post


Link to post
Share on other sites
1 hour ago, PWaddict said:

What is your page field value type? I have it on "Single page Page or boolean false when none selected".

Bingo! Thanks a lot @PWaddict. Of course it does make a difference whether it is a PageArray or a Page. In my case I need to stick to a PageArray but obviously set_part_image.title is not what I need. "Luckily" set_part_image.first.title does work, meaning the issue is solved!

On a side note, I need a PageArray because the InputField Type is Visual Page Selector which currently supports PageArrays only.

Cheers,

Edited by szabesz
typo
  • Like 2

Share this post


Link to post
Share on other sites

One more question regarding generated page names: currently different values referenced in "Name format children" are concatenated by a dash character separating them. Can I somehow use underscore instead?

That way I could easily tell the various values apart even in the generated name.

Share this post


Link to post
Share on other sites
21 hours ago, szabesz said:

That way I could easily tell the various values apart even in the generated name.

Since I am dealing with children of PageTables which do not need any public names/urls I use the title instead which is much more meaningful anyway. I realized that I do not even need this module for what I want to achieve. It just seemed convenient at first sight to use it, instead I switched to using my own hook in order to do whatever I need.

Share this post


Link to post
Share on other sites

@kixe I want to use an Options field as part of the pagename but I don't get anything. On the Name format for children I tried with: title my_options_field and with title my_options_field.title but I only get the pagename from the title field.

  • Like 1

Share this post


Link to post
Share on other sites

@kixe The 175 line of the module is causing the issue:

if (wire('fields')->get($format) && wire('fields')->get($format)->type instanceof FieldtypeOptions) $value = $page->get($format)->get('value|title');

I had to change this to this in order to get the title of the options field:

if (wire('fields')->get($format) && wire('fields')->get($format)->type instanceof FieldtypeOptions) $value = $page->get($format)->title;

 

Additional languages for the options field are ignored cause I'm only getting the default one for all page names.

Please check it out and update the module. Thanks.

Share this post


Link to post
Share on other sites

@kixe I've updated the module to 2.1.1 and now I can't even save the page. I'm getting the following error: Method SelectableOptionArray::getLanguageValue does not exist or is not callable in this context

  • Like 1

Share this post


Link to post
Share on other sites
12 minutes ago, kixe said:

@PWaddict

Sorry. I fixed the bug. Please update to  2.1.2

With the 2.1.2 the page is getting saved but when I'm editing the related fields the page names for alternate languages are not getting updated.

Share this post


Link to post
Share on other sites

@kixe I've added on the options field all the options in all languages and now the page names for alternate languages are getting updated. The problem is that the option value is getting injected on the page names instead of the option title.

Share this post


Link to post
Share on other sites

The idea is to generate the page name from field values and not from labels. I will not change this. But I added support for dot syntax for the options fieldtype which should feed your needs.
 

// no fallback to default language if not set. Options should be populated in each language

my_options_field.title
my_options_field.value
my_options_field.id

// always fallback to default language. If values are set pagename is pulled from the value, otherwise from title

my_options_field

 

  • Thanks 1

Share this post


Link to post
Share on other sites

i'm getting errors when this module is installed, using the latest version of PW. Had to uninstall it to remove the error; this is ok in my situation as i wasn't doing anything complex; but would be good to see if this can be fixed somehow.. TIA

Admin_Bug_Reporting_Here_on_Elliott_Carter_Website___Trello.thumb.jpg.289871736bff01188fe9d621c9368e6e.jpg

Share this post


Link to post
Share on other sites

I'm getting the same error with PW 3.0.62. I installed it, updated my parent template with the format I wanted to use and then went to create a child page.

I got the error, uninstalled the module as suggested by Macrura and refreshed the page I was trying to create and got redirected to page/edit/?id=XXXX&new=1 and it had created the name/title in the format I'd specified.

Now I can create more child pages which automatically skip the add new page and have the expected name/title format, even though the module is no longer installed.

Share this post


Link to post
Share on other sites

@kixe can you please update the module to display the warning "SetupPageName expects value in field 'my_field' to autogenerate Pagename" ONLY on debug mode? It's not user friendly and it can confuse site editors who have no idea about these stuff as it displayed instantly when adding a new page.

Replacing the 236 line with this would do the trick:

if ($warning === true) $this->warning(sprintf($format_warning, $format), Notice::debug);

 

Share this post


Link to post
Share on other sites
On 1/29/2019 at 11:58 PM, Macrura said:

i'm getting errors when this module is installed, using the latest version of PW. Had to uninstall it to remove the error; this is ok in my situation as i wasn't doing anything complex; but would be good to see if this can be fixed somehow.. TIA

Confirmed, same error using PW  3.0.123 and 2.1.3 module version, in my case still doesn't work even after uninstalled the module.

Fatal Error: Uncaught Error: Call to a member function get() on null in ...\site\assets\cache\FileCompiler\site\modules\ProcessSetupPageName\ProcessSetupPageName.module:129
Stack trace:
#0 ...\site\assets\cache\FileCompiler\site\modules\ProcessSetupPageName\ProcessSetupPageName.module(298): ProcessSetupPageName->createFromFormat(Object(ProcessWire\Page), 'parent.title')
#1 ...\wire\core\Wire.php(386): ProcessSetupPageName->___SetupPageName(Object(ProcessWire\Page), Array)
#2 ...\wire\core\WireHooks.php(723): ProcessWire\Wire->_callMethod('___SetupPageNam...', Array)
#3 ...\wire\core\Wire.php(442): ProcessWire\WireHooks->runHooks(Object(ProcessSetupPageName), 'SetupPageName', Array)
#4 ...\site\assets\cache\FileCompiler\site\modules\ProcessSetupPageName\ProcessSetupPageName.module(93): ProcessWire\Wire->__call('SetupPageName', Array)
#5 ...\wire\core\WireHooks.php(813): ProcessSetupPageName->{closure}(Object(ProcessWire\HookEv (line 129 of ...\site\assets\cache\FileCompiler\site\modules\ProcessSetupPageName\ProcessSetupPageName.module) 

 

 

Share this post


Link to post
Share on other sites

@jonassalen, open the ProcessSetupPageName.module file in your code editor and try replacing this section at the top of the createFromFormat() method...

if ($languageID == null && $this->languageSupport == true) $languageID = $this->wire('languages')->getDefault()->id;
$langID = $this->wire('languages')->get($languageID)->isDefault()? null : $languageID;

if ($this->languageSupport) {
	$userLang = $this->wire('user')->language;
	$this->wire('user')->language = $this->wire('languages')->get($languageID);
}

...with...

$langID = null;
if ($this->languageSupport) {
	if ($languageID == null) $languageID = $this->wire('languages')->getDefault()->id;
	$langID = $this->wire('languages')->get($languageID)->isDefault()? null : $languageID;
	$userLang = $this->wire('user')->language;
	$this->wire('user')->language = $this->wire('languages')->get($languageID);
}

 

  • Like 2

Share this post


Link to post
Share on other sites

@Robin S thanks for that! That got the basic functions of the module to work for me.

I may be missing something, but is part of the function of this module to give the child pages titles as well as names? The names are working, but the page titles are not being constructed according to the naming convention I'm assigning via the module.

Share this post


Link to post
Share on other sites
On 7/6/2019 at 5:47 AM, thistimj said:

I may be missing something, but is part of the function of this module to give the child pages titles as well as names?

No, I don't think the module sets page titles. I was expecting something similar using the core "Name format for children" feature, but if you want to automatically set a title you have to use a hook. It's discussed in the topic below:

 

Share this post


Link to post
Share on other sites
On 7/2/2019 at 12:27 AM, Robin S said:

@jonassalen, open the ProcessSetupPageName.module file in your code editor and try replacing this section at the top of the createFromFormat() method...


if ($languageID == null && $this->languageSupport == true) $languageID = $this->wire('languages')->getDefault()->id;
$langID = $this->wire('languages')->get($languageID)->isDefault()? null : $languageID;

if ($this->languageSupport) {
	$userLang = $this->wire('user')->language;
	$this->wire('user')->language = $this->wire('languages')->get($languageID);
}

...with...


$langID = null;
if ($this->languageSupport) {
	if ($languageID == null) $languageID = $this->wire('languages')->getDefault()->id;
	$langID = $this->wire('languages')->get($languageID)->isDefault()? null : $languageID;
	$userLang = $this->wire('user')->language;
	$this->wire('user')->language = $this->wire('languages')->get($languageID);
}

 

Sorry for not looking in here. I replaced the code as recommended by @Robin S without further testing and hope it works well now. I didn't use the module by myself for a long time. Stay healthy!

Share this post


Link to post
Share on other sites

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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
    • By Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
×
×
  • Create New...