Jump to content

Recommended Posts

That does sound like a great idea indeed. Ever think we'd have any validation issues? (May not even be a valid question - just popped into my head as I was thinking "raw import".)

Also, surely this would only apply to WP sites that are not URL-friendly? Or does Google also happen to index those horrid ?p={id} things anyway?

Share this post


Link to post
Share on other sites

I just looked a a single example Wordpress site, which happend to have the pretty url in the canonical tag. So google shouldn't know about the ugly ones as long as you're using only pretty urls.

Share this post


Link to post
Share on other sites

Well it's just that WP URL's often have the date in the URL and there are a few different format options. Of course this could be replicated in PW, but typically it isn't, so I was mostly wanting to redirect from the pretty WP format to the PW format.

Share this post


Link to post
Share on other sites

So, we'd be looking to redirect /2015/01/hello-world to /blog/hello-world, for example?

Would a simple call like this suffice:

$jumplinks = $modules->get('ProcessJumplinks');
$jumplinks->add('{year}/{month}/{path}','blog/{path}');

--

Side note: would you mind renaming this topic to "Module: Jumplinks" and moving it up to "Modules/Plugins"? (also, I think the tags should go...)

I just don't want to open up a new topic when I release the final.

  • Like 1

Share this post


Link to post
Share on other sites

So, we'd be looking to redirect /2015/01/hello-world to /blog/hello-world, for example?

Would a simple call like this suffice:

$jumplinks = $modules->get('ProcessJumplinks');
$jumplinks->add('{year}/{month}/{path}','blog/{path}');

--

Side note: would you mind renaming this topic to "Module: Jumplinks" and moving it up to "Modules/Plugins"? (also, I think the tags should go...)

I just don't want to open up a new topic when I release the final.

Actually, I think you are right. Although there might need to be a slight variation on that, depending on the WP source format.

I hadn't ever looked at the canonical link info, so knowing that is set up correctly, I guess we don't need to worry about those ID based links - guess there really isn't much to do afterall :)

PS the "k" man beat me to moving this thread! 

Share this post


Link to post
Share on other sites

Actually, I think you are right. Although there might need to be a slight variation on that, depending on the WP source format.

I hadn't ever looked at the canonical link info, so knowing that is set up correctly, I guess we don't need to worry about those ID based links - guess there really isn't much to do afterall :)

PS the "k" man beat me to moving this thread! 

There would indeed - you'd have to parse that out for each segment, and then send it off to Jumplinks.

Does the migrator automatically handle URI changes? (I may just be having a blonde moment here...)

Share this post


Link to post
Share on other sites
Does the migrator automatically handle URI changes? 

Sorry - not sure what you mean here - changes from when till when? Sorry, now I think I am the one having the blonde moment :)

Share this post


Link to post
Share on other sites

Sorry - not sure what you mean here - changes from when till when? Sorry, now I think I am the one having the blonde moment :)

Got confused because you asked for a feature, and with good reason, and then you said it's not needed any more. For some reason, or the other, I assumed that the migrator handles old/new URIs and redirects accordingly... (I haven't used the module, so I don't know it's feature-set.)

Or I'm missing something  :huh:

Share this post


Link to post
Share on other sites

First post cleaned up as documentation is [mostly] ready.

Module is now stable, from what I can tell, though v1 can only be released when PW 2.6 is released. (I'm assuming this is still a little while away... yes?)

  • Like 2

Share this post


Link to post
Share on other sites

Yeah, I did see that - just thought maybe someone could throw in a few hints. ;-)

Because the module is pretty much done, and ready for release (I've even just made a few screencasts which I'll upload in the morning), I'm now wondering (again) if I should make this compatible with 2.5. I guess I jumped over to the 2.6-requirement because I just love the new ModuleConfig. But, I'm sure there are quite a few people who won't be moving over to 2.6 immediately, and that would like to use Jumplinks. So I think I'll just do it.

  • Like 1

Share this post


Link to post
Share on other sites

I would probably keep this 2.6 only. Most use is when releasing new site, so probably most usage will be with latest and greatest ;)

Share this post


Link to post
Share on other sites

I would probably keep this 2.6 only. Most use is when releasing new site, so probably most usage will be with latest and greatest ;)

Indeed, though it's a bit late. Done already. Hehe! And it works with 2.6

_________

Last round of bug-hunting (help would be awesome) before I release v1 tomorrow morning.

  • Like 1

Share this post


Link to post
Share on other sites

@adrian - I have added an API method, I'm sure it will come in handy.

$this->modules->ProcessJumplinks->add(string $source, string $destination, string $start = '', string $end = '')

I think that the WP migrator module should check the permalink format being used (%year%/%monthnum%/%postname%/, for example) and convert it to the Jumplinks-equivalent ({year}/{month}/{name}/, in this case).

  • Like 3

Share this post


Link to post
Share on other sites

Some issues have popped up (regarding timestamps, paths in Windows, execute hyphens, etc) and, thanks to Dave's help in finding them, they have been fixed. Also rolled back to Beta (bumped to 1.0.2 - leaving the version in v1 state) in case any more anomalies pop up.

  • Like 1

Share this post


Link to post
Share on other sites

I'll need to look into this... not sure what's making it require PHP 5.5...

(Going to quickly test on an 5.4, and 5,3 to see what the problem could be.)

Share this post


Link to post
Share on other sites

Ah, it seems that empty() is the culprit here, requiring write access to its argument.

Have pushed the fix to the repo. Works on 5.4 now. (As for 5.3, I don't know yet, but it could well just be fine.)

  • 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 Gadgetto
      SnipWire - Snipcart integration for ProcessWire
      Snipcart is a powerful 3rd party, developer-first HTML/JavaScript shopping cart platform. SnipWire is the missing link between Snipcart and the content management framework ProcessWire.
      With SnipWire, you can quickly turn any ProcessWire site into a Snipcart online shop. The SnipWire plugin helps you to get your store up and running in no time. Detailed knowledge of the Snipcart system is not required.
      SnipWire is free and open source licensed under Mozilla Public License 2.0! A lot of work and effort has gone into development. It would be nice if you could donate an amount to support further development:

      Status update links (inside this thread) for SnipWire development
      2020-04-06 -- SnipWire 0.8.6 (beta) released! Adds support for Snipcart subscriptions and also fixes some problems 2020-03-21 -- SnipWire 0.8.5 (beta) released! Improves SnipWires webhooks interface and provides some other fixes and additions 2020-03-03 -- SnipWire 0.8.4 (beta) released! Improves compatibility for Windows based Systems. 2020-03-01 -- SnipWire 0.8.3 (beta) released! The installation and uninstallation process has been heavily revised. 2020-02-08 -- SnipWire 0.8.2 (beta) released! Added a feature to change the cart and catalogue currency by GET, POST or SESSION param 2020-02-03 -- SnipWire 0.8.1 (beta) released! All custom classes moved into their own namespaces. 2020-02-01 -- SnipWire is now available via ProcessWire's module directory! 2020-01-30 -- SnipWire 0.8.0 (beta) first public release! (module just submitted to the PW modules directory) 2020-01-28 -- added Custom Order Fields feature (first SnipWire release version is near!) 2020-01-21 -- Snipcart v3 - when will the new cart system be implemented? 2020-01-19 -- integrated taxes provider finished (+ very flexible shipping taxes handling) 2020-01-14 -- new date range picker, discount editor, order notifiactions, order statuses, and more ... 2019-11-15 -- orders filter, order details, download + resend invoices, refunds 2019-10-18 -- list filters, REST API improvements, new docs platform, and more ... 2019-08-08 -- dashboard interface, currency selector, managing Orders, Customers and Products, Added a WireTabs, refinded caching behavior 2019-06-15 -- taxes provider, shop templates update, multiCURL implementation, and more ... 2019-06-02 -- FieldtypeSnipWireTaxSelector 2019-05-25 -- SnipWire will be free and open source Plugin Key Features
      Fast and simple store setup Full integration of the Snipcart dashboard into the ProcessWire backend (no need to leave the ProcessWire admin area) Browse and manage orders, customers, discounts, abandoned carts, and more Multi currency support Custom order and cart fields Process refunds and send customer notifications from within the ProcessWire backend Process Abandoned Carts + sending messages to customers from within the ProcessWire backend Complete Snipcart webhooks integration (all events are hookable via ProcessWire hooks) Integrated taxes provider (which is more flexible then Snipcart own provider) Useful Links
      SnipWire in PW modules directory SnipWire Docs (please note that the documentation is a work in progress) SnipWire @GitHub (feature requests and suggestions for improvement are welcome - I also accept pull requests) Snipcart Website  
      ---- INITIAL POST FROM 2019-05-25 ----
       
    • By bernhard
      #######################
      Please use the new RockFinder2
      #######################
      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://github.com/BernhardBaumrock/RockFinder
       
      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 MoritzLost
      TrelloWire
      This is a module that allows you to automatically create Trello cards for ProcessWire pages and update them when the pages are updated. This allows you to setup connected workflows. Card properties and change handling behaviour can be customized through the extensive module configuration. Every action the module performs is hookable, so you can modify when and how cards are created as much as you need to. The module also contains an API-component that makes it easy to make requests to the Trello API and build your own connected ProcessWire-Trello workflows.
      Features
      All the things the module can do for you without any custom code: Create a new card on Trello whenever a page is added or published (you can select applicable templates). Configure the target board, target list, name and description for new cards. Add default labels and checklists to the card. Update the card whenever the page is updated (optional). When the status of the card changes (published / unpublished, hidden / unhidden, trashed / restored or deleted), move the card to a different list or archive or delete it (configurable). You can extend this through hooks in many ways: Modifiy when and how cards are created. Modify the card properties (Target board & list, title, description, et c.) before they are sent to Trello. Create your own workflows by utilizing an API helper class with many convenient utility methods to access the Trello API directly. Feedback & Future Plans
      Let me know what you think! In particular:
      If you find any bugs report them here or on Github, I'll try to fix them. This module was born out of a use-case for a client project where we manage new form submissions through Trello. I'm not sure how many use-cases there are for this module. If you do use it, tell me about it! The Trello API is pretty extensive, I'll try to add some more helper methods to the TrelloWireApi class (let me know if you need anything in particular). I'll think about how the module can support different workflows that include Twig – talk to me if you have a use-case! Next steps could be a dashboard to manage pages that are connected to a Trello card, or a new section in the settings tab to manage the Trello connection. But it depends on whether there is any interest in this 🙂 Links
      Repository on Github Complete module documentation (getting started, configuration & API documentation) [Module directory pending approval] Module configuration

    • By MoritzLost
      Process Cache Control
      This module provides a simple solution to clearing all your cache layers at once, and an extensible interface to perform various cache-related actions.
      The simple motivation behind this module was that I was tired of manually clearing caches in several places after deploying a change on a live site. The basic purpose of this module is a simple Clear all caches link in the Setup menu which clears out all caches, no matter where they hide. You can customize what exactly the module does through it's configuration menu:
      Expire or delete all cache entries in the database, or selectively clear caches by namespace ($cache API) Clear the the template render cache. Clear out specific folders inside your site's cache directory (/site/assets/cache) Clear the ProCache page render cache (if your site is using ProCache) Refresh version strings for static assets to bust client-side browser caches (this requires some setup, see the full documentation for details). This is the basic function of the module. However, you can also add different cache management action through the API and execute them through the module's interface. For this advanced usage, the module provides:
      An interface to see all available cache actions and execute them. A system log and logging output on the module page to see verify what the module is doing. A CacheControlTools class with utility functions to clear out different caches. An API to add cache actions, execute them programmatically and even modify the default action. Permission management, allowing you granular control over which user roles can execute which actions. The complete documentation can be found in the module's README.
      Plans for improvements
      If there is some interest in this, I plan to expand this to a more general cache management solution. I particular, I would like to add additional cache actions. Some ideas that came to mind:
      Warming up the template render cache for publicly accessible pages. Removing all active user sessions. Let me know if you have more suggestions!
      Links
      https://github.com/MoritzLost/ProcessCacheControl ProcessCacheControl in the Module directory CHANGELOG in the repository Screenshots


    • By Macrura
      PrevNextTabs Module
      Github: https://github.com/outflux3/PrevNextTabs
      Processwire helper modules for adding page navigation within the editor.
      Overview
      This is a very simple module that adds Previous and Next links inline with the tabs on the page editor. Hovering over the tab shows the title of the previous or next page (using the admin's built in jqueryUI tooltips.)
      Usage
      This module is typically used during development where you or your editors need to traverse through pages for the purpose of proofing, flagging and/or commenting. Rather than returning to the page tree or lister, they can navigate with these links.
      Warnings
      If you are using PW version 2.6.1 or later, the system will prevent you from leaving the page if you have unsaved edits.
      For earlier versions, to avoid accidentally losing changes made to a page that might occur if a user accidentally clicks on one of these, make sure to have the Form Save Reminder module installed.
      http://modules.processwire.com/modules/prev-next-tabs/
×
×
  • Create New...