Jump to content
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

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

  • Like 1

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 5

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 5

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?

 

  • Like 1

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

 

  • Like 1

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