wumbo

Module: FieldtypeAssistedURL

Recommended Posts

Thank you for testing it, Adrian!

I will try to find out why it isn't working for me. It's just a local page to play and to get deeper into PW.

Share this post


Link to post
Share on other sites
2 minutes ago, sms said:

Thank you for testing it, Adrian!

I will try to find out why it isn't working for me. It's just a local page to play and to get deeper into PW.

Perhaps you have checked one of these two options in the settings for this module:

Prepend site's root path to local/relative URLs?
Allow relative/local URLs without "http://" at the beginning?

Either of those will break the lookup of the page for getting the title.

But again, Page Reference is much better for local links - one of the key reasons is that is stores the page ID which never changes, rather than the URL which may possibly break down the road.

  • Like 1

Share this post


Link to post
Share on other sites

Thank you very much again. I have checked and unchecked these options but it doesn't work for me. But the Page Reference works perfectly:

<a href="<?php echo $page->link->url; ?>"><?php echo $page->link->title; ?></a>

:-)

  • Like 1

Share this post


Link to post
Share on other sites
On 8.3.2017 at 0:34 PM, pmichaelis said:

Hey,

thanks for that module. 

Maybe I missed something, but how to get the propoerties, like target, title, or rel in a page template?
Are these values stored anywhere?

Thanks for help.

Sorry, that I need to post my question again. Is there a chance for storing these values to the db?

Share this post


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

Is there a chance for storing these values to the db?

Not in this fieldtype as it stands because it only has a single inputfield. But you can create other fields for the purpose and add them to your template, maybe grouped inside a fieldset together with the Assisted URL field. Text fields for title and rel, and maybe a Select Options field would be good for target.

Share this post


Link to post
Share on other sites
11 hours ago, Robin S said:

Not in this fieldtype as it stands because it only has a single inputfield. But you can create other fields for the purpose and add them to your template, maybe grouped inside a fieldset together with the Assisted URL field. Text fields for title and rel, and maybe a Select Options field would be good for target.

Ok, thanks for the reply. I was just wondering, because the modal dialog keeps all these options. An altnernative would be to store the data (url, title, rel, target) as json in order to have them.

Share this post


Link to post
Share on other sites

Hello,

When I install this module I get this error:

 

Parse error: syntax error, unexpected '[' in ....../html/site/assets/cache/FileCompiler/site/modules/FieldtypeAssistedURL/FieldtypeAssistedURL.module on line 26

What could be the reason for this. Please help!

Share this post


Link to post
Share on other sites

Someone has already asked but... no way for multi-language?
I think that multi-language support should be the first thing to take care when developing a new module :)

Share this post


Link to post
Share on other sites

Hi,

I'm using the module "AssistedURL Field" inside a repeater. It works fine when I'm logged in as superuser. When I'm logged in with restricted rights (user account), I get this error when I click the button to select a URL:

Modules: Error initializing module: ProcessPageEditLink - You don't have access to this page

The error appears within the appearing modal window of "AssistedURL Field" in which the URL or page can be selected.

What am I missing?

Edited by kongondo
Moderator Note: Moved question to the module's support forum.

Share this post


Link to post
Share on other sites

Strange thing: If I give the user the same rights as the superuser, the error will still persist!

There is also a second error:

ProcessWire: The requested process does not exist

 

Bildschirmfoto 2018-01-16 um 10.10.27.png

Share this post


Link to post
Share on other sites

I have completely uninstalled and reinstalled the module, now. I also emptied the module cache. The error still exists. I'm greatly appreciated for any hint.

Share this post


Link to post
Share on other sites

@nabo For multilingual url fields maybe you could try this module with https://github.com/ryancramerdesign/FieldtypeURLLanguage?

Sorry @anyway, I'm not sure.  Maybe you can list the permission of the user's roles?  Does the user's role have the page-edit permission?  Did you enable access control for the field?  Edit the field and click on the "Access" tab to check.

Share this post


Link to post
Share on other sites
On 15/01/2018 at 10:35 PM, anyway said:

I get this error when I click the button to select a URL:


Modules: Error initializing module: ProcessPageEditLink - You don't have access to this page

I can confirm the problem. When the inputfield is inside a repeater item the module tries to open the link modal for the repeater page, but non-superusers do not have direct access to repeater pages. The core link modal (opened from CKEditor) does not have this problem because in the case of being inside a repeater item it opens the link modal for the container page instead.

You can apply the same logic to this module by editing InputfieldAssistedURL.module, changing line 62...

$btn->attr('data-page-id', $this->page->id);

...to (edit: there could be multiple nested repeaters, so best to borrow the code from ProcessPageEditLink)...

$page = $this->page;
$n = 0;
while(wireInstanceOf($page, 'RepeaterPage') && ++$n < 10) {
    $page = $page->getForPage();
}
$btn->attr('data-page-id', $page->id);

 

  • Like 1

Share this post


Link to post
Share on other sites

@gmclelland Thanks for your reply! Yes, the user's role has the page-edit permission. In the meantime, I've been able to "solve" the problem by giving page-view access to the system template "admin" to the user role Page-View, which is probably not optimal.

@Robin S Unfortunately, your code doesn't work for me. The repeater elements can no longer be opened. There is only a short twitch when you click on the elements. Any idea?

ProcessWire 3.0.62

 

 

Share this post


Link to post
Share on other sites
9 minutes ago, anyway said:

Unfortunately, your code doesn't work for me. The repeater elements can no longer be opened. There is only a short twitch when you click on the elements. Any idea?

Not sure. It works for me in PW 3.0.88. Seems like it could be a Javascript error - check your browser console to see if that reveals any issues.

assisted.gif.e821c5c765ae2a34b87058ad7a176340.gif

Share this post


Link to post
Share on other sites

You're right, it looks like a javascript error, but the console does not show any errors. After the click, the elements appear to open (the three dots disappear), but the accordions doesn't drop down.

Share this post


Link to post
Share on other sites
On 7/29/2015 at 2:07 PM, adrian said:

When selecting a page from the site, I would rather the field stores the ID of the page, just in case the path (and therefore the URL) is changed down the road.

Well, I am using this field for the first time and really wanted this functionality, so decided to fork the module here: 
https://github.com/adrianbj/processwire-fieldtype-assisted-url

It doesn't look any different from the users perspective, but on save/sleep it stores the page ID instead of the url and then on wakeup it converts to ID back to the URL.

This means that you can now move a page to a different parent, rename it, etc and the link URL will be automatically updated. 

It doesn't look like @wumbo is still active around here, so not sure if this will make it into the main version of the module, but it's there if others want it.

  • Like 4

Share this post


Link to post
Share on other sites

A few more enhancements:

It now handles local links with query string parameters - the stored link is still converted to a page ID with the query string appended. 

You can now also paste full http(s) links and if these are local links, they will be converted to a page ID and a local link will be returned when the value is requested.

  • Like 4

Share this post


Link to post
Share on other sites

One more small, but pretty important tweak - it now properly removes the tabs at the top in the UiKit theme. Important so that users aren't confused by the useless "Attributes" tab option.

I think I am pretty happy with it now that it is storing page IDs for local links, but I am  curious if anyone else is still using this module? Is there something else out there that I might have missed that provides a nice interface for choose links to local pages and also has the option to paste in an external link?

 

Share this post


Link to post
Share on other sites

Thanks for the feedback @gmclelland - I don't have the need (and therefore the time) to look into the multilanguage side of things right now, but if others want to contribute, I am happy to maintain this fork going forward. Perhaps if we could get @wumbo to chime in to confirm he's no longer to going to support this, I could point the entry in the modules directory to my fork?

PS - I just emailed him via the address listed on his Github profile and it bounced and it's the same address he has used in his PW modules directory account. I don't have access to check the email for his forum account, but I am guessing these notifications are probably bouncing too. I don't really feel right switching things out without his permission, but also not sure how to move forward - anyone have any thoughts on this? I think maybe PW needs a policy on this, because it's bound to happen again with other modules.

PPS - I found another email address for him, so hopefully I will hear something soon.

  • Like 2

Share this post


Link to post
Share on other sites

I've been using this field and appreciated the string of page IDs for PW pages.

I'm wondering if instead of converting the ID to a URL before returning it, how about returning an object?

So, Instead of $page->AssistedURL returning just a string "/mypage/" (internal) or "http://www.anothersite.com/" (external), it returns the object:

// Internal PW page
{
    'id' => 1234,
    'name' => 'mypage',
    'url' => '/mypage/',
    'httpUrl' => 'http://my-processwire-root.com/mypage/'
}

// External link
{
    'id' => 0,                                 // 0 or null
    'name' => '',                              // blank or null
    'url' => 'http://www.anothersite.com/',
    'httpUrl' => 'http://www.anothersite.com/' // url and httpUrl are the same for external links
}

// Accessing the data
$page->AssistedURL->id
$page->AssistedURL->name
$page->AssistedURL->url
$page->AssistedURL->httpUrl

For backwards compatibility, could $page->AssistedURL by itself be a magic method to return the URL as it currently does?

By returning relative and absolute links, the same field could be used in multiple situations (eg, on an internal menu, and in an email template).

 

  • Like 2

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
      WHY?
      This module was built to fill the gap between simple $pages->find() operations and complex SQL queries.
      The problem with $pages->find() is that it loads all pages into memory and that can be a problem when querying multiple thousands of pages. Even $pages->findMany() loads all pages into memory and therefore is a lot slower than regular SQL.
      The problem with SQL on the other hand is, that the queries are quite complex to build. All fields are separate tables, some repeatable fields use multiple rows for their content that belong to only one single page, you always need to check for the page status (which is not necessary on regular find() operations and therefore nobody is used to that).
      In short: It is far too much work to efficiently and easily get an array of data based on PW pages and fields and I need that a lot for my RockGrid module to build all kinds of tabular data.

      Basic Usage

       
      Docs & Download
      https://modules.processwire.com/modules/rock-finder/
      https://gitlab.com/baumrock/RockFinder/tree/master
       
      Changelog
      180817, v1.0.6, support for joining multiple finders 180810, v1.0.5, basic support for options fields 180528, v1.0.4, add custom select statement option 180516, change sql query method, bump version to 1.0.0 180515, multilang bugfix 180513, beta release <180513, preview/discussion took place here: https://processwire.com/talk/topic/18983-rocksqlfinder-highly-efficient-and-flexible-sql-finder-module/
    • By OLSA
      Hello for all,
      ConfigurationForm fieldtype module is one my experiment from 2016.
      Main target to build this module was to store multiple setup and configuration values in just 1 field and avoid to use 1 db table to store just single "number of items on page", or another db table to store "layout type" etc. Thanks to JSON formatted storage this module can help you to reduce number of PW native fields in project, save DB space, and reduce number of queries at front-end.
      Install and setup:
      Download (at the bottom ), unzip and install like any other PW module (site/modules/...). Create some filed using this type of field (ConfigurationForm Fieldtype) Go to field setup Input tab and drag some subfields to container area (demo). Set "Name" and other params for subfields Save and place field to templates ("Action tab") How to use it:
      In my case, I use it to store setup and configurations values, but also for contact details, small content blocks... (eg. "widgets").
      Basic usage example:
      ConfigForm fieldtype "setup" has subfields:
      "limit", type select, option values: 5, 10, 15, 20
      "sort", type select, option values: "-date", "date",  "-sort", "sort"
      // get page children (items) $limit = isset($page->setup->limit) ? $page->setup->limit : 10; $sort = isset($page->setup->sort) ? $page->setup->sort : '-sort'; $items = $page->children("limit=$limit, sort=$sort");  
      Screenshots:


       
      Notes:
      Provide option to search inside subfields Provide multilanguage inputs for text and textarea field types Provide option for different field layout per-template basis Do not place/use field type "Button" or "File input" because it won't works. Please read README file for more details and examples Module use JSON format to store values. Text and textarea field types are multilanguage compatible, but please note that main target for this module was to store setup values and small content blocks and save DB space. Search part inside JSON is still a relatively new in MySQL (>=5.77) and that's on you how and for what to use this module.
      Thanks:
      Initial point for this fieldtype was jQuery plugin FormBuiled and thanks to Kevin Chappel for this plugin.
      In field type "link" I use javascript part from @marcostoll module and thanks to him for that part.
      Download:
      FieldtypeConfigForm.zip
      Edit: 14. August 2018. please delete/uninstall previously downloaded zip
      Regards.
         
    • By bernhard
      @Sergio asked about the pdf creation process in the showcase thread about my 360° feedback/survey tool and so I went ahead and set my little pdf helper module to public.
      Description from PW Weekly:
       
      Modules Directory: https://modules.processwire.com/modules/rock-pdf/
      Download & Docs: https://gitlab.com/baumrock/RockPdf
       
      You can combine it easily with RockReplacer: 
      See also a little showcase of the RockPdf module in this thread:
       
    • By Thomas Diroll
      Hi guys I'm relatively new to PW and just finished developing a page for a client. I was able to include all necessary functionality using the core fieldtypes but now I it seems that I need to extend them with a custom one. What I need is a simple button, that copies the absolute url (frontend not PW-backend) of the page which is currently edited to the clipboard. As this feature is only needed inside a specific template, I tend to use a custom fieldtype which provides this feature. I've been looking inside the core modules code (eg. FieldtypeCheckbox.module) but I don't really get the structure of it and how its rendered to the admin page. I also didn't find a lot of tutorials covering custom fieldtypes.
      Maybe some of you could give me some tips on how to write a basic custom fieldtype that renders a button which copies the value of
      page->httpUrl() to the clipboard using JS. Thanks!
    • By bernhard
      Some of you might have followed the development of this module here: https://processwire.com/talk/topic/15524-previewdiscussion-rockdatatables/ . It is the successor of "RockDataTables" and requires RockFinder to get the data for the grid easily and efficiently. It uses the open source part of agGrid for grid rendering.
       
      WHY?
      ProcessWire is awesome for creating all kinds of custom backend applications, but where it is not so awesome in my opinion is when it comes to listing this data. Of course we have the built in page lister and we have ListerPro, but none of that solutions is capable of properly displaying large amounts of data, for example lists of revenues, aggregations, quick and easy sorts by the user, instant filter and those kind of features. RockGrid to the rescue 😉 
       
      Features/Highlights:
      100k+ rows Instant (client side) filter, search, sort (different sort based on data type, eg "lower/greater than" for numbers, "contains" for strings) extendable via plugins (available plugins at the moment: fullscreen, csv export, reload, batch-processing of data, column sum/statistics, row selection) all the agGrid features (cell renderers, cell styling, pagination, column grouping etc) vanilla javascript, backend and frontend support (though not all plugins are working on the frontend yet and I don't plan to support it as long as I don't need it myself)  
      Limitations:
      While there is an option to retrieve data via AJAX the actual processing of the grid (displaying, filtering, sorting) is done on the client side, meaning that you can get into troubles when handling really large datasets of several thousands of rows. agGrid should be one of the most performant grid options in the world (see the official example page with a 100k row example) and does a lot to prevent problems (such as virtual row rendering), but you should always have this limitation in mind as this is a major difference to the available lister options that do not have this limitation.
      Currently it only supports AdminThemeUikit and I don't plan to support any other admin theme.
       
      Download: https://gitlab.com/baumrock/RockGrid
      Installation: https://gitlab.com/baumrock/RockGrid/wikis/Installation
      Quikckstart: https://gitlab.com/baumrock/RockGrid/wikis/quickstart
      Further instructions: https://gitlab.com/baumrock/RockGrid/wikis/quickstart#further-instructions
       
      Module status: alpha, License: MIT
      Note that every installation and uninstallation sends an anonymous google analytics event to my google analytics account. If you don't want that feel free to remove the appropriate lines of code before installation/uninstallation.
       
      Contribute:
      You can contribute to the development of this and other modules or just say thank you by
      testing, reporting issues and making PRs at gitlab liking this post buying me a drink: paypal.me/baumrock/5 liking my facebook page: facebook.com/baumrock hiring me for pw work: baumrock.com  
      Support: Please note that this module might not be as easy and plug&play as many other modules. It needs a good understanding of agGrid (and JavaScript in general) and it likely needs some looks into the code to get all the options. Please understand that I can not provide free support for every request here in the forum. I try to answer all questions that might also help others or that might improve the module but for individual requests I offer paid support for 60€ per hour.
       
      Changelog
      180730 support subdir installations 180711 bugfix (naming issue) 180630 alpha realease  
      Use Cases / Examples:
      Colored grid cells, Icons, Links etc. The Grid also has a "batcher" feature built in that helps communicating with the server via AJAX and managing resource intensive tasks in batches:

      Filters, PW panel links and instant reload on panel close:

      You can combine the grid with a chart library like I did with the (outdated) RockDataTables module: