Jump to content
wumbo

Module: FieldtypeAssistedURL

Recommended Posts

After install @adrian version. I got this error:

Error: Call to undefined function wireInstanceOf() (line 64 of /oath/to/site/modules/FieldtypeAssistedURL/InputfieldAssistedURL.module)

I am using Processwire 3.0.42 and PHP 5.5.9

Any Ideas??

 

Gideon

 

Share this post


Link to post
Share on other sites

I think that function wireInstanceOf() is not available in 3.0.42. Upgrade to the latest master.

Share this post


Link to post
Share on other sites

Hi all,

I see that @wumbo mentioned that the 'Link Attributes' where specifically removed from the modal which pops up.

However is it possible to enable the 'Link Attributes' tab for this field type, seems like it would be very useful for my current project.

 

Share this post


Link to post
Share on other sites

@adrian

Hi Adrian, 

I know you have done the latest version of this module. I'm having a few issues using your folk on 3.0, not entirely sure if it's me. 

1. You mentioned that it sets a sleep value of the page ID, so if the URL is to ever change it will be update. This doesn't seem to be working at all. I can set it to a local url but it does not update if I change the url.
2. It doesn't seem to store ID's at all on a local install. 

I think both of the above is because it's installed on a folder: I mean the domain is http://dev.agency.com/client - so the url is /client/link/to/page and exactly why I need 1 or 2 for when it goes live. 

I'm going to do a folk and fix that. Let me know if you want to merge. 

  • Like 1

Share this post


Link to post
Share on other sites
5 hours ago, Tom. said:

Let me know if you want to merge. 

Please!

Share this post


Link to post
Share on other sites

Hi,

Wondering if anyone can advise on the following 2 use cases for site running at https://example.com (so $config->httpHosts array in config.php contains example.com)

  1. Want to create link to https://subdomain.example.com however cannot do this as example.com is present and so looks for an internal link
  2. Want to create a mailto link such as mailto:user@example.com however cannot do this.

Changing the site to run at www.example.com solves (1) but does not solve (2).

Thanks in advance for any advice.

 

Share this post


Link to post
Share on other sites
On 2/19/2018 at 9:33 PM, adrian said:

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.

Hi @adrian I've downloaded the most up to date files from your branch and have overwritten the original module files in a site I am working on.  I've refreshed the modules in the admin too, but I just can't get the urls to update if a page is moved or its url is changed. Do you know if I am missing something really simple? I thought it may have been because I am trying to do this retrospectively to existing assisted url field but I tried creating a new field and the problem still persists. Any help of advice would be greatly appreciated.

Thanks
Dave

Share this post


Link to post
Share on other sites

@999design - Hi Dave,

I just tested to make sure everything was still good, and it is here.

Can you please take a look in the DB to confirm it's storing the page ID, eg:

image.png.d0696d137de1331c38737cceb420db50.png

Just to clarify, this won't work on old stored data - it's only for links added since this version has been running.

 

Share this post


Link to post
Share on other sites

Hi @adrian Just checked and yes, it's storing the page ID. I'm probably doing something really stupid. I double checked the module files and everything matches your fork.

Share this post


Link to post
Share on other sites

Any chance your running procache or there is some other caching going on?

Are you looking at the link that is being output on the frontend, or in the admin within the field where it displays the relative URL?

Perhaps you can debug at what point things are not working within the logic in the module?

Share this post


Link to post
Share on other sites

I've been checking on the front end and in the admin. Have also tried on an incognito window but no joy. I don't have caching set on the pages either.

I'll try to have a look through the module and see what I can find.

Thanks for the quick replies, much appreciated.

Share this post


Link to post
Share on other sites

Apologies for the delayed reply. Was working on a deadline when I raised this issue and completely forgot to leave an update.

It suddenly began to work and I'm not quite sure why but I suspect that it was a caching thing, or maybe as you suggested regarding only updating new entries. It's filtered through all the links using this now that were previously not updating so I'm happy either way 😃

Thanks for all your help here @adrian.

  • Like 1

Share this post


Link to post
Share on other sites

Converting relative URLs to page IDs doesn't seem to work if there is more than 1 URL segment (/page1/subpage/) AND the application is NOT running in a subdirectory.

I had to replace line 86 from FieldtypeAssistedURL.module

$urlPage = "/" . str_replace($this->wire('config')->urls->root, "", $urlParts[0]);

with

if($this->wire('config')->urls->root !== '/') {
	$urlPage = "/" . str_replace($this->wire('config')->urls->root, "", $urlParts[0]);
} else {
	$urlPage = $urlParts[0];
}

to make it work.

Am I missing something? 

  • Like 1

Share this post


Link to post
Share on other sites

Thanks @dynweb - for some reason I hadn't noticed that. I have committed your fix. 

Thanks again.

  • Like 1

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