Jump to content

Recommended Posts

Find attached the first Alpha Version of the Module ProcessSetupPageName with Multilanguage Support. I tested it under various circumstances and it is doing fine with one exception: Until now it doesn't work together with 'Page Name Extended' (since PW 3.0.12) which allows UTF8 Page Names. Module requires PHP >= 5.4.x
Download from here:
EDIT: Removed link, download last version from here: https://github.com/kixe/ProcessSetupPageName/archive/master.zip

Would be nice if you could test it and give a feedback to me. Thanks in advance.

Edited by kixe
Due to some updates, I replaced the download link.
  • Like 3

Share this post


Link to post
Share on other sites

There the error with the new file.

Error: Cannot access self:: when no class scope is active (line 70 of ../site/assets/cache/FileCompiler/site/modules/ProcessSetupPageName-master/ProcessSetupPageName.module)

For use it I just remove the self::$notes and replace by ''.

Share this post


Link to post
Share on other sites

@Filkaboy
Which PHP Version do you use? Both Errors you mentioned looking like PHP = 5.3.x Could you make an update of your PHP Version and try again? Thanks.

Fatal error: Using $this when not in object context in /site/modules/ProcessSetupPageName-master/ProcessSetupPageName.module on line 68

Error: Cannot access self:: when no class scope is active (line 70 of ../site/assets/cache/FileCompiler/site/modules/ProcessSetupPageName-master/ProcessSetupPageName.module)

Share this post


Link to post
Share on other sites

@Filkaboy

Which PHP Version do you use? Both Errors you mentioned looking like PHP = 5.3.x Could you make an update of your PHP Version and try again? Thanks.

Yes exactly the problem... my previews version of php 5.3 and now with 5.5 all work fine.

Thank you

  • Like 1

Share this post


Link to post
Share on other sites

Great module but there's one thing that prevents me form using it, maybe this could be added in the future:

When adding a page and in the middle of the process you decide not to add a new page (skipping the Publish button and navigate away), then an empty page will be created. I think this coul be solved by adding a "Cancel" button next to the existing buttons ("Publish", "Save and....", "Cancel"). But perhaps there is an easier fix.

Don't get me wrong - I can delete the pages of course but I would use this module to make it easier for clients to add new pages, especially where the page name is actually irrelevant.

As a bonus feature request I would love to see message like these appear only for superusers - these may be too much for a regular client:

"SetupPageName expects value in field 'title' to autogenerate Pagename"

  • Like 1

Share this post


Link to post
Share on other sites

Ryan solved this in pagetable as that pages created but not published are deleted automatically each day by a kind of lazycron. On mobile and no details for that... Just throwing in an idea

  • Like 1

Share this post


Link to post
Share on other sites

When adding a page and in the middle of the process you decide not to add a new page (skipping the Publish button and navigate away), then an empty page will be created. I think this coul be solved by adding a "Cancel" button next to the existing buttons ("Publish", "Save and....", "Cancel"). But perhaps there is an easier fix.

In fact the page is already created in the 'middle of the process' and it has to be created to pull the page name from other page fields. If you don't like this. Create a cronjob like bernhard mentioned. Example:

$wire->addHook('LazyCron::everyDay', function() {
    // trash untitled pages
    $delay = time()-60;
    $untitleds = wire('pages')->find("created<$delay,name^=untitled,include=all");
    foreach ($untitleds as $untitled) $untitled->trash(); // to delete permanently use $untitled->delete() instead
});
Don't get me wrong - I can delete the pages of course but I would use this module to make it easier for clients to add new pages, especially where the page name is actually irrelevant.

In this case you don't need this module. Use built in 'Name Format Children' in parent template settings and create the name frome date. It is also possible in my module to create the name from any autogenerated page property like 'created' or 'id'. Read the note in 'Name Format Children' field if module is installed.

As a bonus feature request I would love to see message like these appear only for superusers - these may be too much for a regular client:

"SetupPageName expects value in field 'title' to autogenerate Pagename"

This message is needed. How could the page editor know from where the values are pulled to generate the pagename? I don't want to change this.

  • Like 2

Share this post


Link to post
Share on other sites

Thanks, I will try a combination of fields then & try lazycron.

This message is needed. How could the page editor know from where the values are pulled to generate the pagename? I don't want to change this.

Sometimes the editors shouldn't care about the page name, for example when pages are created to hold content for content blocks. For example awards pages that won't have its own page at all.

  • Like 1

Share this post


Link to post
Share on other sites

As I said use built in options in this case. Read more here: https://processwire.com/api/modules/process-template/

To create contentblocks you can also use Repeaters (single template). Or better ProFields RepeaterMatrix (multiple templates). Repeaters are stored as pages too but very hidden and you don't need to care about naming.

Share this post


Link to post
Share on other sites

Hi, I was trying this module, and I get this error:

Error: Uncaught Error: Call to a member function getDefault() on null in /Users/krlos/Documents/Sitios/processpdf/site/modules/ProcessSetupPageName/ProcessSetupPageName.module:99

Processwire: 2.7.2

PHP: 7.0.0

Share this post


Link to post
Share on other sites
On 2016/7/11 at 10:51 AM, Krlos said:

Hi, I was trying this module, and I get this error:


Error: Uncaught Error: Call to a member function getDefault() on null in /Users/krlos/Documents/Sitios/processpdf/site/modules/ProcessSetupPageName/ProcessSetupPageName.module:99

Processwire: 2.7.2

PHP: 7.0.0

I also get this error and found that this is due to the lack of  a core module called "Languages Support". The error is gone after install the module.

I suggest to add "Languages Support" to the dependency of this module.

Share this post


Link to post
Share on other sites

Hi,

this module throws an error when I create a new page.

Call to a member function getLanguageValue() on a non-object (Zeile 121 in /var/www/_html_default/processwire-playground/site/modules/ProcessSetupPageName/ProcessSetupPageName.module)


My name format for children is "date(Y/m/d) title", LanguageSupport is installed but the title field has the type PageName, not PageNameLanguage.

In this case, $page->title is a plain string, so this seems to work for me:

        // case 2: title default
        else if ($format == 'title') {
            if(is_object($page->title) && strlen($page->title->getLanguageValue($languageID))) {
                $pageName .= '-'.$page->title->getLanguageValue($languageID);
            } else {
                $pageName .= '-'.$page->title;
            }
        }

Further investigation might be necessary: Can $page->title->getLanguageValue(...) be an empty string?

Share this post


Link to post
Share on other sites

Hi,

it seems the module throws errors, when used together with Version Control. Pages which have version control enabled generate this error message.

I am not very good at php, so I cant investigate this further, but I would like to use this module. ATM I cant run the site without version control.

Uncaught Error: Call to a member function get() on null in /Applications/MAMP/htdocs/wire/core/Pages.php:321
Stack trace:
#0 /Applications/MAMP/htdocs/wire/core/WireArray.php(1933): ProcessWire\Pages->get('setModuleConfig...')
#1 /Applications/MAMP/htdocs/wire/core/WireArray.php(2149): ProcessWire\WireArray->implode('ProcessVersionC...', 'setModuleConfig...', Array)
#2 [internal function]: ProcessWire\WireArray->___callUnknown('setModuleConfig...', Array)
#3 /Applications/MAMP/htdocs/wire/core/Wire.php(374): call_user_func_array(Array, Array)
#4 /Applications/MAMP/htdocs/wire/core/WireHooks.php(549): ProcessWire\Wire->_callMethod('___callUnknown', Array)
#5 /Applications/MAMP/htdocs/wire/core/Wire.php(399): ProcessWire\WireHooks->runHooks(Object(ProcessWire\Modules), 'callUnknown', Array)
#6 /Applications/MAMP/htdocs/wire/core/Wire.php(402): ProcessWire\Wire->__call('callUnknown', Array)
#7 /Applications/MAMP/htdocs/site/mo (Zeile 321 in /Applications/MAMP/htdocs/bluevr/wire/core/Pages.php) 

PW: 3.0.39

Share this post


Link to post
Share on other sites

@Krlos @Karl_T

On 11.7.2016 at 4:51 AM, Krlos said:

Hi, I was trying this module, and I get this error:


Error: Uncaught Error: Call to a member function getDefault() on null in /Users/krlos/Documents/Sitios/processpdf/site/modules/ProcessSetupPageName/ProcessSetupPageName.module:99

 

I fixed the single/ multilanguage issue. Sorry for the delay ...
Please update to 2.0.1 and try out.

  • Like 1

Share this post


Link to post
Share on other sites

How can I display on the backend the pages created with this module as titles instead of names?

For example I'm currently see the pages as: test-30-jan-2017. How can I see them as: Test 30 Jan 2017?

Sorry that was my mistake.

Share this post


Link to post
Share on other sites

@kixe Are you planning to make the module to update the page name when the fields that used to generate the name have been edited?

Share this post


Link to post
Share on other sites
On 13.2.2017 at 1:02 PM, PWaddict said:

@kixe Are you planning to make the module to update the page name when the fields that used to generate the name have been edited?

@PWaddict Thanks for the input. I made the module configurable with the option you mentioned. Furthermore I did some repairings for some special cases. Seems to work. Please try Version 2.0.2

  • Like 2

Share this post


Link to post
Share on other sites
8 hours ago, kixe said:

@PWaddict Thanks for the input. I made the module configurable with the option you mentioned. Furthermore I did some repairings for some special cases. Seems to work. Please try Version 2.0.2

I just tried it and unfortunately it doesn't work at all. I tried with both checked and unchecked the option just in case that was the problem.

Share this post


Link to post
Share on other sites
9 hours ago, kixe said:

I made the module configurable with the option you mentioned.

Perhaps there should be some warning about this option in the readme and/or module config page, as it has the potential to inadvertently break links if the Page Path History module is not installed.

  • Like 1

Share this post


Link to post
Share on other sites
4 hours ago, PWaddict said:

I just tried it and unfortunately it doesn't work at all. I tried with both checked and unchecked the option just in case that was the problem.

I am sorry about that. Did you get any Errors? Exceptions? Please let me know. I tested the module in 2 different environments. It worked there without problems.

@Robin S

Thanks for the hint. I added a note to the config field and the readme.

  • Like 1

Share this post


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

I am sorry about that. Did you get any Errors? Exceptions? Please let me know. I tested the module in 2 different environments. It worked there without problems.

There are no errors. It's just doesn't update the page name. I'm on localhost with php 7 and ProcessWire 3.0.52.

Share this post


Link to post
Share on other sites

@PWaddict

I missed to add the hook which update pagenames even if language support isn't enabled. I fixed this in Version 2.0.3
If you use the module in single language mode this might have been the cause. Thanks for your help.

  • Like 2

Share this post


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

@PWaddict

I missed to add the hook which update pagenames even if language support isn't enabled. I fixed this in Version 2.0.3
If you use the module in single language mode this might have been the cause. Thanks for your help.

Yep that was the problem. Now it's working perfect. Thank you very much.

  • Like 1

Share this post


Link to post
Share on other sites

@kixe I'm using a multi-language datetime field on the name format for children and it doesn't work properly. I'm using this format: %b %d, %Y and it can't update the page name with the format %b. It seems that it can only update the numeric formats.

Instead of getting this page name:
jan-22-2018

I'm getting this:
b-22-2018

Can you please fix it?

Share this post


Link to post
Share on other sites

The module uses php function date() and NOT strftime(). To get what you expect use the following format string: 'date(M-d-Y)'.

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 bernhard
      --- Please use RockFinder3 ---
    • By MoritzLost
      Cacheable Placeholders
      This module allows you to have pieces of dynamic content inside cached output. This aims to solve the common problem of having a mostly cacheable site, but with pieces of dynamic output here and there.  Consider this simple example, where you want to output a custom greeting to the current user:
      <h1>Good morning, <?= ucfirst($user->name) ?></h1> This snippet means you can't use the template cache (at least for logged-in users), because each user has a different name. Even if 99% of your output is static, you can only cache the pieces that you know won't include this personal greeting. A more common example would be CSRF tokens for HTML forms - those need to be unique by definition, so you can't cache the form wholesale.
      This module solves this problem by introducing cacheable placeholders - small placeholder tokens that get replaced during every request. The replacement is done inside a Page::render hook so it runs during every request, even if the response is served from the template cache. So you can use something like this:
      <h1>Good morning, {{{greeting}}}</h1> Replacement tokens are defined with a callback function that produces the appropriate output and added to the module through a simple hook:
      // site/ready.php wire()->addHookAfter('CachePlaceholders::getTokens', function (HookEvent $e) { $tokens = $e->return; $tokens['greeting'] = [ 'callback' => function (array $tokenData) { return ucfirst(wire('user')->name); } ]; $e->return = $tokens; }); Tokens can also include parameters that are parsed and passed to the callback function. There are more fully annotated examples and step-by-step instructions in the README on Github!
      Features
      A simple and fast token parser that calls the appropriate callback and runs automatically. Tokens may include multiple named or positional parameters, as well as multi-value parameters. A manual mode that allows you to replace tokens in custom pieces of cached content (useful if you're using the $cache API). Some built-in tokens for common use-cases: CSRF-Tokens, replacing values from superglobals and producing random hexadecimal strings. The token format is completely customizable, all delimiters can be changed to avoid collisions with existing tag parsers or template languages. Links
      Github Repository & documentation Module directory (pending approval) If you are interested in learning more, the README is very extensive, with more usage examples, code samples and usage instructions!
    • By Craig
      I've been using Fathom Analytics for a while now and on a growing number of sites, so thought it was about time there was a PW module for it.
      WayFathomAnalytics
      WayFathomAnalytics is a group of modules which will allow you to view your Fathom Analytics dashboard in the PW admin panel and (optionally) automatically add and configure the tracking code on front-end pages.
      Links
      GitHub Readme & documentation Download Zip Modules directory Module settings screenshot What is Fathom Analytics?
      Fathom Analytics is a simple, privacy-focused website analytics tool for bloggers and businesses.

      Stop scrolling through pages of reports and collecting gobs of personal data about your visitors, both of which you probably don't need. Fathom is a simple and private website analytics platform that lets you focus on what's important: your business.
      Privacy focused Fast-loading dashboards, all data is on a single screen Easy to get what you need, no training required Unlimited email reports Private or public dashboard sharing Cookie notices not required (it doesn't use cookies or collect personal data) Displays: top content, top referrers, top goals and more
    • By daniels
      This is a lightweight alternative to other newsletter & newsletter-subscription modules.
      You can find the Module in the Modules directory and on Github
      It can subscribe, update, unsubscribe & delete a user in a list in Mailchimp with MailChimp API 3.0. It does not provide any forms or validation, so you can feel free to use your own. To protect your users, it does not save any user data in logs or sends them to an admin.
      This module fits your needs if you...
      ...use Mailchimp as your newsletter / email-automation tool ...want to let users subscribe to your newsletter on your website ...want to use your own form, validation and messages (with or without the wire forms) ...don't want any personal user data saved in any way in your ProcessWire environment (cf. EU data regulation terms) ...like to subscribe, update, unsubscribe or delete users to/from different lists ...like the Mailchimp UI for creating / sending / reviewing email campaigns *I have only tested it with PHP 7.x so far, so use on owners risk
      EDIT:
      Since 0.0.4, instructions and changelog can be found in the README only. You can find it here  🙂
      If you have questions or like to contribute, just post a reply or create an issue or pr on github, thanks!
    • By MoritzLost
      Sorry for the convoluted title. I have a problem with Process modules that define a custom page using the page key through getModuleInfo (as demonstrated in this excellent tutorial by @bernhard). Those pages are created automatically when the module is installed. The problem is that the title of the page only gets set in the current language. That's not a problem if the current language (language of the superuser who is installing the module) is the default language; if it isn't, the Process page is missing a title in the default language. This has the very awkward effect that a user using the backend in the default language (or any other language) will see an empty entry in the setup menu:

      This screenshot comes from my Cache Control module which includes a Process page. Now I realize the description sounds obscure, but for us it's a common setup: We a multiple bilingual sites where the default language is German and the second language is English. While the clients use the CMS in German, as a developer I prefer the English interface, so whenever I install a Process module I get this problem.
      As a module author, is there a way to handle this situation? I guess it would be possible to use post-installation hooks or create the pages manually, but I very much prefer the declarative approach. The page title is already translatable (through the __ function), but of course at the time of installation there is no translation, and as far as I'm aware it's not possible to ship translations with a module so they are used automatically. Could this situation be handled better in the core? I would prefer if the module installation process would always set the title of the Process page in the default language, instead of the language of the current user.
×
×
  • Create New...