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 MoritzLost
      This module allows you to integrate hCaptcha bot / spam protection into ProcessWire forms. hCaptcha is a great alternative to Google ReCaptcha, especially if you are in the EU and need to comply with privacy regulations.

      The development of this module is sponsored by schwarzdesign.
      The module is built as an Inputfield, allowing you to integrate it into any ProcessWire form you want. It's primarily intended for frontend forms and can be added to Form Builder forms for automatic spam protection. There's a step-by-step guide for adding the hCaptcha widget to Form Builder forms in the README, as well as instructions for API usage.
      Features
      Inputfield that displays an hCaptcha widget in ProcessWire forms. The inputfield verifies the hCaptcha response upon submission, and adds a field error if it is invalid. All hCaptcha configuration options for the widget (theme, display size etc) can be changed through the inputfield configuration, as well as programmatically. hCaptcha script options can be changed through a hook. Error messages can be translated through ProcessWire's site translations. hCaptcha secret keys and site-keys can be set for each individual inputfield or globally in your config.php. Error codes and failures are logged to help you find configuration errors. Please check the README for setup instructions.
      Links
      Github Repository and documentation InputfieldHCaptcha in the module directory (pending approval) Screenshots (configuration)

      Screenshots (hCaptcha widget)

       
       

       
    • By joshua
      This module is (yet another) way for implementing a cookie management solution.
      Of course there are several other possibilities:
      - https://processwire.com/talk/topic/22920-klaro-cookie-consent-manager/
      - https://github.com/webmanufaktur/CookieManagementBanner
      - https://github.com/johannesdachsel/cookiemonster
      - https://www.oiljs.org/
      - ... and so on ...
      In this module you can configure which kind of cookie categories you want to manage:

      You can also enable the support for respecting the Do-Not-Track (DNT) header to don't annoy users, who already decided for all their browsing experience.
      Currently there are four possible cookie groups:
      - Necessary (always enabled)
      - Statistics
      - Marketing
      - External Media
      All groups can be renamed, so feel free to use other cookie group names. I just haven't found a way to implement a "repeater like" field as configurable module field ...
      When you want to load specific scripts ( like Google Analytics, Google Maps, ...) only after the user's content to this specific category of cookies, just use the following script syntax:
      <script type="text/plain" data-type="text/javascript" data-category="statistics" data-src="/path/to/your/statistic/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing" data-src="/path/to/your/mareketing/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="external_media" data-src="/path/to/your/external-media/script.js"></script> <script type="text/plain" data-type="text/javascript" data-category="marketing">console.log("Inline scripts are also working!");</script> The type has to be "optin" to get recognized by PrivacyWire, the data-attributes are giving hints, how the script shall be loaded, if the data-category is within the cookie consents of the user. These scripts are loaded asynchronously after the user made the decision.
      If you want to give the users the possibility to change their consent, you can use the following Textformatter:
      [[privacywire-choose-cookies]] It's planned to add also other Textformatters to opt-out of specific cookie groups or delete the whole consent cookie.
      You can also add a custom link to output the banner again with a link / button with following class:
      <a href="#" class="privacywire-show-options">Show Cookie Options</a> <button class="privacywire-show-options">Show Cookie Options</button> This module is still in development, but we already use it on several production websites.
      You find it here: PrivacyWire Git Repo
      Download as .zip
      I would love to hear your feedback 🙂
      CHANGELOG
      0.1.1 Debugging: fixed error during uninstall 0.1.0 Added new detection of async scripts for W3C Validation 0.0.6 CSS-Debugging for hiding unused buttons, added ProCache support for the JavaScript tag 0.0.5 Multi-language support included completely (also in TextFormatter). Added possibility to async load other assets (e.g. <img type="optin" data-category="marketing" data-src="https://via.placeholder.com/300x300">) 0.0.4 Added possibility to add an imprint link to the banner 0.0.3 Multi-language support for module config (still in development) 0.0.2 First release 0.0.1 Early development
    • 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
×
×
  • Create New...