Module: FieldtypeAssistedURL

[sms]

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.

[adrian]

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.

[sms]

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>

[pmichaelis]

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?

[Robin S]

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.

[pmichaelis]

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.

[MaryMatlow]

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!

[Macrura]

@MaryMatlow what version of PHP are you using? You do need to be on 5.4+

[MaryMatlow]

PHP was 5.6.21 but changed it to version 7 and now it works fine.  Thank you @Macrura

[nabo]

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

[anyway]

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 January 15, 2018 by kongondo
Moderator Note: Moved question to the module's support forum.

[anyway]

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

 

[anyway]

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.

[gmclelland]

@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.

[Robin S]

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);

 

[anyway]

@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

 

 

[Robin S]

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.

[anyway]

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.

[adrian]

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.

[adrian]

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.

[adrian]

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?

 

[gmclelland]

Thanks for doing this @adrian.  I use it.  To me that was the one main missing feature of this module.  I think other people have also asked for multilingual support, but maybe that can be fulfilled with https://github.com/ryancramerdesign/FieldtypeURLLanguage in combination with this module?

[adrian]

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.

[adrian]

On 1/16/2018 at 12:54 PM, Robin S said:

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

Thanks Robin - you saved me some time figuring this out - much appreciated. I have pushed this change to my fork here: https://github.com/adrianbj/processwire-fieldtype-assisted-url

 

[LMD]

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).