Leaderboard

Hello everybody, It's another day - so it's time for a new module and this module is all about helping your site's visitors to store the pages they want to visit. Bookmarks is a module that delivers a straightforward API for storing pages, adding bookmark-comments and tags to them. You can create a bookmark for the current user for a page with a single line of code: $page->bookmark->save(); You can also add comments and tags to it: $page->bookmark->comment = 'Early in the morning'; $page->bookmark->tags = array('sleepy', 'bashful', 'sneezy'); $page->bookmark->save(); After having stored some bookmarks, you can fetch a user's bookmarks in this way: $user->bookmarks; You can find a live demo of the module here: http://nickel-1vn.lightningpw.com/ You can find the module and additional APIs here: https://github.com/conclurer/PageBookmarks The module is submitted for the module directory and should appear soon. Please leave a comment below to add feedback and / or feature wishes. Thanks in advance, Marvin

Hi all, This one is special because it's for a project of ours, Erika and mine. http://muesli-cafe.com/ We are starting a crowdfunding campaign to open a breakfast place in Porto where we will serve muesli. This is quite a bold attempt because muesli is not common at all in Portugal and it will take a good communication effort from our part. We will need all the help we can get, if you guys want to contribute here's the project's crowdfunding page http://ppl.com.pt/en/prj/muesli-cafe-porto and you will be all welcome to Porto to taste our delicacies It will be great if we make it

We've recently rebrushed/relaunched our agencys website and took the opportunity to build it using processwire (as we're currently using it for almost all of our projects). http://www.neuwaerts.de Modules used: Modules Manager Page Link Abstractor Database Backups Redirects Revision History For Text Fields Template Data Providers Template Decorator Template Twig Replace There currently are 6(!) more websites using processwire in the making (more or less parallel) so stay tuned for some more showcase entrys in the next weeks

When I started working on my first ProcessWire site I liked that by simply opening the basic-page.php template file (obviously connected to basic-page template), I could instantly see how everything worked. It was easy to start from there, building more complexity and adding those "advanced tricks" if/when needed. Things like delayed output, appendTemplateFile/prependTemplateFile, etc. raise the bar of entry, that's just how it works. They're things you won't simply "get on the first sight". You'll have to dig through other template, config and README files (or docs) to understand what's going on. However you look at it, things that "just magically do something" may be helpful and ease your workload once you understand how they work, but also tend to add to the frustration a new user feels getting used to the system. Personally I believe that the "first dive" into a new system should be as easy and enjoyable as possible. Anything that complicates things is likely to increase the bounce rate.

This module adds CSV import and export functionality to Profields Table fields on both the admin and front-end. http://modules.processwire.com/modules/table-csv-import-export/ https://github.com/adrianbj/TableCsvImportExport Access to the admin import/export for non-superusers is controlled by two automatically created permissions: table-csv-import and table-csv-export Another permission (table-csv-import-overwrite) allows you to control access to the overwrite option when importing. The overwrite option is also controlled at the field level. Go to the table field's Input tab and check the new "Allow overwrite option" if you want this enabled at all for the specific field. Please consider limiting import overwrite option to trusted roles as you could do a lot of damage very quickly with the overwrite option Front-end export of a table field to CSV can be achieved with the exportCsv() method: // export as CSV if csv_export=1 is in url if($input->get->csv_export==1){ $modules->get('ProcessTableCsvExport'); // load module // delimiter, enclosure, file extension, multiple fields separator, names in first row $page->fields->tablefield->exportCsv('tab', '"', 'tsv', '|', true); } // display content of template with link to same page with appended csv_export=1 else{ include("./head.inc"); echo $page->tablefield->render(); //render table - not necessary for export - just displaying the table echo "<a href='./?csv_export=1'>Export Table as CSV</a>"; //link to initiate export include("./foot.inc"); } Front-end import can be achieved with the importCsv() method: $modules->get('TableCsvImportExport'); // load module // data, delimiter, enclosure, convert decimals, ignore first row, multiple fields separator, append or overwrite $page->fields->tablefield->importCsv($csvData, ';', '"', true, false, '|', 'append'); Please let me know if you have any problems, or suggestions for improvements. Enjoy!

Hi All, I have been away for several months I guess. Just too much stuff going on. A couple of my MODx sites have just been hacked. So, my learning of all things Processwire now takes on a new urgency. I have four or more sites to convert to PW as soon as I am able. The timing is not perfect but plunging into the deep end is probably a good thing. Anyway, I just wanted to say how impressed I am with all the new effort I see on the PW site: new tuts, new profiles, new cool version of of the application and lots of new documentation & forum chatter... Cheers, Max

Update: Today the last of the four sites went online. This last one is by far the biggest one: ~20.000 users, each with profile options which are searchable in this section: http://lu-web.de/lu-links/ (search for "Hannover" for example), additional options are available when "Nach Qualifikationen filtern" is clicked. Also there are eMagazines which are only viewable if the user is logged in and has an active subscription. To sum up: http://schaedlings.net http://kommunaltechnik.net http://beckmann-verlag.de http://lu-web.de

When I rewrite my old simple site tutorial, I will be recommending the blank install and then I will take the most logical route so that the html is really staring people in the face. If the HTML is recognisable and familiar, they will have a better chance of understanding what they need to learn. However, I will, as I have done before, make sure that new users realise that this is not what you MUST do, but rather what you CAN do. The problem with tutorials, as with demo installs, is that you have to decide on just one method to avoid confusion - it is difficult to avoid newcomers believing that this is the way they have to do things.

There are days where I get a huge great, miserable reminder than I am a composer/writer/advertising bloke, and not a sysadmin, coder or expert anything. Warning: if some bright spark has a solution for this, don't tell me - its too late. Having had a couple of odd problems I decided that I really ought to update php on my little Ubuntu dev box. It is 12.04 with Webmin installed. Turns out that this is not very easy to do - generally, the Ubuntu repositories only let you install the php that comes with your distribution - 12.04 only comes with 5.3. However, I found a neat little tutorial that added a repository so that you can upgrade - it is maintained by some of the debian folk. So, I went and did that. Trouble is, it also went and updated Apache to 2.4 (much to my surprise) and everything went wrong. First of all, Apache wouldn't start. It was complaining about everything. I spent 2 hours reading posts from everywhere and nothing worked. So, I uninstalled it, purged it and reinstalled it. Yep, it started! Except now, it would not recognise ANY of the virtual hosts. I started reading again. I tried creating new hosts in Virtualmin, but Apache did not want to know. I tried manually - still not interested. I read every post out there and tried every trick - but the things they said would be definitely wrong were fine, except the working thing. I tried a couple of other things which included restarting apache. Guess what? It wouldn't start again - gave off the same errors. I had backed up all my sites with Virtualmin, so I tried restoring them to see if I could force it to work. Nothing. So, I have found myself staring at a development server that isn't - serving that is. And, what is more, my meagre knowledge has simply run out, as has my patience. So, I have just double backed up everything - files, MySQL and the rest and I have just downloaded a new ISO of Ubuntu. And with that, I am going to reinstall the entire thing, format all the crap away into PBS Telethon, sort out some partitioning woes I had in the process (my old boot partition was too small, really) and start from scratch. It is not clever, it is not educational and it is a sledgehammer solution - but when you are not the Demon Sysadmin of Fleet Street, sledgehammers might be all you have left.

IMPORTANT - DO NOT USE THIS FOR A PRODUCTION SERVER This is not strictly a ProcessWire tutorial, except it really is very useful for developing ProcessWire websites. I have just rebuilt my little dev server and it was a right pain - basically, I made the mistake of following a couple of bits of really bad advice. I eventually nailed down the right thing to do in the right order from about three different sources and have decided to write it up. This tutorial will take you through installing a pristine, new version of Ubuntu on an old PC, setting it up to work on your local network (this is NOT a publicly facing server), installing Virtualmin, Samba window shares, and setting up your first virtual server. The main problem I found with the help that I followed, is that no one seemed to link all these install processes together - so a standard install of Ubuntu with Apache would completely mess up Virtualmin and make it all a nightmare. This is a PDF file without screenshots, but to be honest, I am not sure how screenshots of command line is particularly helpful to anyone! Feel free to use this and let me know if it actually worked. NOTE: I am not a sysadmin, so if you find strange errors, you are more likely to find the answer through Google than by asking me - this is just the result of me pulling my hair out for a day or so. I certainly cannot guarantee that this is perfect or even the best way. Installing Ubuntu and Webmin.pdf

He uses a CropImagefield, and the Error is explainend exactly! in the link I have posted in my first answer. And it is not another error, it is exactly the same, because there is only one place in PW pageimage / imagesizer where this is done, (writing Errormessages into a image-variation.). So please, @julbr, read the explanation in the thread I have linked too. There is also described that you can open the image-variation and or the original image in a simple Texteditor to see what the error was when trying to resize / upload the image. Can you tell me what there is to read. Also the filesize is only a few Bytes.

I'm doing PW sites for almost four years now I think and still be using head.inc and foot.inc and do some $template->render() stuff for parts of my site. So I think you can just use the way you're more comfortable with.

@sunlix: you might want to take a look at how I've handled this issue in the Changelog module. The approach I took there was adding new configuration option ($this->schema_version, which refers to the schema version currently used) and a constant (SCHEMA_VERSION, which refers to latest available schema version) and until those match it'll run updateDatabaseSchema() method, which takes care of schema updates. In that case the install routine actually uses an "outdated" schema version, so that module update (on existing installation) and fresh module installation behave exactly the same. That's definitely a question of preference. This is actually a simplified version of ProcessWire's own SystemUpdater.. and pretty much what @netcarver mentioned above too

Hi everybody, I'd like to share with you another new module. It helps you to manage user ratings for pages in a very simple way. You can add a user rating to a certain page with a line of code: $page->ratings->add(4) If the user is logged in, the module remembers which page the user has rated for. For non-logged-in visitors, the module stores the pages, the user has rated, in the session. You can get a page's rating and its total amount of votes in a similar way: $page->ratings->average; // => 3.2 $page->ratings->count; // => 5 For more information about this module, please check out its GitHub repository. You can check out a working version of the module here: http://curium-cte.lightningpw.com Edit: The module is now available in the ProcessWire modules directory. Update: Ratings has been updated to version 1.1, including a new, simpler API accessor. As always - please comment for bugs or feature wishes. Thanks in advance, Marvin

Hello again! We've just updated Ratings to Version 1.1, which includes a simpler, more unified API. You can access all API methods via the ratings property. Examples: $page->ratings->add(4); $page->ratings->average; // => 4.4 $page->ratings->count; // => 12 The changes should appear soon in the ProcessWire modules directory. Please check out our GitHub repository for more details.

$serverField = $modules->get("InputfieldText"); $serverField->label = "Server Name"; $serverField->attr("id+name","servername"); $serverField->attr("value",$prefillServer); $serverField->attr("class","form-control"); $serverField->description = "this is my description";//this is the right syntax $serverForm->append($serverField);

Today the second site out of a series of 4 went online. This project is a bit different than the usual websites I do. The client had 4 websites, 3 of them running on a very old school proprietary CMS and one on MODX Evolution. I developed a layout which gets adapted by all three of them with minor differences and functions. I am running these on one installation of PW with the multi site module "Soma edition", originally by Apeisa. No problems so far with that. I imported around 1500 documents for both of the sites by fitting the CSV importer module to my needs. I could also manage to import images/PDFs which were hard coded in the shitty CMS by extracting the src from the markup. The PW-API surprised me a lot while doing this, just try&success ;-) The sites share a lot of templates, I tried to build it as modular as possible. As always, the CropImage module is loved by the clients and it also serves different image sizes for the sliders, while the picture polyfill loads the correct one dependent on the visitors screen size. The only thing I am struggling at the moment is the performace of the backend. Sometimes no problems, sometimes significant loading times. I am not quite sure if this is a server performance issue or is something related to PW. I also customized the backend a bit for quick create/edit pages: Ryan, if you read this: Do you think it is possible to get ProCache up and running for multi site environments? I think it would be a good benchmark, because the last site which gets converted will be the biggest one. And I am a bit concerned about perfomance (will be 10000+ pages). So, here are the two (warning: german and pretty boring, something with public vehicles and something with pests & ugly banners): http://kommunaltechnik.net http://schaedlings.net

@sforsman: you should never not post a module only because you can't maintain it. Just do it like me: release it and then declare it as "proof of concept"

Felix, Oh mein Gott! Das ist wunderbar! Ihre Website sehen sehr professionell. Es ist sehr kreativ. Ich wünschte, ich hätte das Niveau der Kreativität, die Sie haben. Sehr schöne Arbeit.

Sorry, I mean "template engine" in the generic sense of building the final view that users see and the process for generating that. I'm not talking about a language like smarty or anything like that. Sorry, I'm not really up on all the lingo and proper terminology for these things. I'm just wary of unnecessary complexity, that is all. What you do in your own ProcessWire install is none of my business After all, the beauty of PW is it's flexibility and the fact that it doesn't force you to do things a certain way. I just know that I would have been turned off if the workings of the PW templates weren't immediately clear to me when I first found it. This is from someone who came from building sites with pure html, pages, css, and a few php includes, so that is the world I'm from, take it or leave it

Hi Sven, An idea off the top of my head (and totally untested): could you make your module a configurable module with a hidden field set to the current module's version. During your init routine you'll get given that value so you just compare it with your module's current version and if your current version is greater then call your update routine to alter the table as needed. Knowing Ryan, there's probably a way to do this built-in but I'm currently unaware of it.

I've updated the module to version 0.5.1 including some minor fixes. New features are the ability to use SSL (LDAPS), turn on Debug Mode and the validation of the configuration file on save. @horst: the typo is also fixed @sforsman: when can I expect your repository? I'd really like to see it.

I love what you've done. I could imagine you can add an extra data cleaner for the importer with the help of json_encode. Forget this, to much much my own module in my mind.

Don't even go there! This is the one that ships with the most recent Ubuntu Its working now though

Note: edited my post above...x2

@OrganizedFellow: Thanks for your report. The module does not write duplicates, on the demo site the output of all bookmarks is grouped by tag. So if you assign multiple tags to one bookmark, the bookmark will show up multiple times. The reason why the bookmark is deleted when you remove it from one tag, is that I was lazy writing the demo, so that the entire bookmark is deleted instead of one tag. The white Save-Button is rather an "update" button than a save button. You can assign or remove tags and change your comment afterwards and then save the bookmark again. Your example is a perfect use case for this module. Great idea!

First get the the pages you want to delete and then delete them.. not searching a reference with a page you already deleted.

Nice guide if you want to develop on a physical server. A year ago or so I switched to developing on virtual servers set up with vagrant. They're a breeze to setup and you can carry them with you wherever you go. Recently I discovered protobox which makes it quite easy to setup virtual machines with preinstalled processwire, wordpress or whatever else.

I just had a panic as I reinstalled one of my virtuals only to get a 500 error. Then, as I went through it, I realised that of all the backups I could have picked, I picked the one with a typo. Typical!

Well, I am eventually up and running, I hope. The result of my labours is here: https://processwire.com/talk/topic/7890-tutorial-setting-up-an-ubuntu-dev-server-with-virtualmin/

I've encountered a bug when entering multiple tags, the bookmark gets saved multiple times. and when I attempt to delete one of the duplicates, they are all deleted. i accidentally saved a bookmark many times, how about disabling the Saved button after the first save? SUPER COOL, I can easily use this for an upcoming project. Would work ideal for a recipe type website.

@valan Not sure if this is related but there's an open issue on github regarding https-only templates (they're meant to redirect from http to https but don't in 2.5) Posting an issue on github might be a faster way of getting a response from Ryan about your problem.

If you want to make license visible in your custom PW Installation, you could place the following few lines in /wire/modules/Process/ProcessModule.module if(!empty($moduleInfo['license'])) { $hreflicense = (!empty($moduleInfo['hreflicense']))?" - <a href='$moduleInfo[hreflicense]'>".$this->_('read more')."</a>":""; $table->row(array($this->_x('License', 'edit'), $moduleInfo['license'].$hreflicense)); } just behind this line (989) if(!empty($moduleInfo['author'])) $table->row(array($this->_x('Author', 'edit'), $moduleInfo['author'])); Now you can set license Name and link to license page in your Modules Info like. public static function getModuleInfo() { return array( // other settings 'license' => 'CC-BY', 'hreflicense' => 'http://creativecommons.org/licenses/by/4.0/' ); } Would be nice to add this option to core.

That's the exact thing I try to avoid @Marvin: Here goes: https://github.com/sforsman/SessionLdapAuth I even added an example for the group mapper and did a modification to the code (well, I fixed a spelling error in the description of the module)! If you have any questions about some parts of it, just ask away. I've published it as a Proof of Concept. (see Nico, I'm learning!) No but really, the main point here is to give you something to think against regarding your own implementation. The group mapper configuration string for an example is parsed in a very quick and dirty (=error prone) way and shouldn't be given directly to clients.

Thanks, Marvin, this is really nice. Are you are using sessions to store the guest's bookmarks? If so, have you considered a cookie solution too so that visitors can come back days later and find their bookmarks again?

Very nice!

Felix, what a great site. So very creative, it's bliss to browse through. The couch idea is just, awesome! +100000 (Even noticed that it randomised the order of the people, which is so cool!) Thinking of releasing an English version?

What version ProcessWire did you use last? I made the jump from 2.3 to 2.5.3 a couple days ago. MAJOR difference. "Lovin' It!"

After site / server is hacked it's important to collect information about it. Is "only" the webspace affected by the hack? Are files changed? Often code is injected to index.html vor index.php files. But code could also be inserted to the database... Are strange processes running (ps aux). Maybe changes made in system / user environment (search /proc with strange process id). Or emails send? Via URL call or a local spawned process? A new listening port or strange traffic (use tcpdump)? Check logs to find hack attempts and maybe the entry point. If attacker reached root permissions binaries (ls, ps, ...) could be replaced to hide things!

Sorry to hear that. Here's a post that might help: https://processwire.com/talk/topic/6736-pharma-hack/ I am also moving this topic to the 'off-topic - dev talk' forum....since it is not directly related to PW...

I'm in the UK right now until Christmas. I'm staying at Croydon, about 10 minutes from central London. Are there any ProcessWire developers nearby?

Hey sforsman! Of course it's a nice thing that PW core uses it's own architecture to provide functionalities, and the whole "modular" idea it's really a big selling point. The modular admin is just awesome, it's like anything is possible. Which I love. I'll have to dive more into hooks and get better used to it, because that's where the extensibility power really lies. In any case thanks everybody for the precious help

Antti, AdminBar seems to hide the template dropdown when adding a new page on ProcessWire 2.5.2 sites. I'm not sure why this particular line was originally added, but removing it fixes the bug: https://github.com/apeisa/AdminBar/blob/master/AdminBar.module#L142 Do you have some idea if this change will cause problems with earlier versions of ProcessWire?

@Peter This might not be exactly what you want but I think you can get a long way towards making things easy using PWs existing per-template label feature for fields. Just edit your Staff Directory template and locate the "title" field in the list of fields and click on the word "title" to bring up the per-template field config sttings editor. You can now change the label for the title field from "Title" to "Full Name" and save that and the template you should now be able to use the title field and it will be displayed as "Full Name" on every page you edit or add. In effect you can re-purpose the title field and remove the need for a separate full_name field. I know that might not be 100% of what you are after but it goes a long way toward it.

@adrian: I have found a workaround for me. I set it up like this: parent installs: child1, child2 parent requires: child1 requires: parent child1 installs: child2 requires: parent child2 installs: I would not need this with my workaround but found it to be usefull to display all those infos about requires and installs in the modules admin. In the Parent uninstall method I use this code: public function ___uninstall() { $GLOBALS['UNINSTALLROUTINE_RUNNING_PARENTNAME'] = array(); foreach(array('ModuleNameChild1', 'ModuleNameChild2') as $mod) { $this->modules->resetCache(); if (!$this->modules->isInstalled($mod)) continue; $GLOBALS['UNINSTALLROUTINE_RUNNING_PARENTNAME'][] = $mod; $m = $this->modules->get($mod); $m->uninstall(); } parent::___uninstall(); } and in the Children uninstall methods: public function ___uninstall() { if (!isset($GLOBALS['UNINSTALLROUTINE_RUNNING_PARENTNAME']) || !in_array(__CLASS__, $GLOBALS['UNINSTALLROUTINE_RUNNING_PARENTNAME'])) { throw new WireException("Please only use the ParentModulesName to uninstall the complete ModulesPackage!"); } parent::___uninstall(); ... This way you can use the ParentModule to uninstall all, but you cannot uninstall one of the Children. A bit weird is, that the children modules get uninstalled two times, , this is because of the auto-install / auto-uninstall routine of PW modules dependencies. But if one would not specify dependencies, this could be avoided, but also the dependency messages will not be displayed then.

Just want to point out that the code diogo posted in #17 uses a relatively new PHP array syntax. If you are running PHP < 5.4 then you will need to do this instead... $images = array("image1.jpg", "image2.jpg", "image3.jpg");

Does your hosting service charge per line?

Just wanted to throw in my two cents. If you come at it as a front-end developer that's a complete beginner to CMSs, then PW should be very easy to get going. It's built around working the same way that existing web technologies work… Pages map in the same way that URLs do… Template files are just plain HTML/PHP files… the API is largely the same as a front-end API (jQuery)… and so on. So if you know your basic web technologies outside of CMSs, then you won't find a simpler system than ProcessWire. The problem is most other CMSs don't work that way. So the line gets more blurry when you've become used to the terminology and approach of another CMS, because PW can be quite different. Sometimes you have to unlearn what you know from elsewhere in order to appreciate the simplicity of PW. People are always trying to find complexity that isn't there, especially those that grew up on other platforms. PW is a system that rewards you by being curious. We aim to show you how to fish so that you can catch the big fish. We're not here to catch the fish for you. You don't have to know anything about fishing, but you should know how to yell for help if you fall in the water. And you should be willing to learn by example. I learn best by example, so this is the way I tend to teach too (and I recognize not everyone learns the same way). PW is a CMS and CMF, not a website builder. If you are curious and willing to explore, you'll find it is very simple indeed. Certainly far simpler than even WordPress in creating a custom website. You do have to come from the point of view of "I want to create and have the system adapt to me" rather than "I will create something based on what the system provides." If you already know what you want to create and it's something unique, you won't find a simpler path to get there than PW. WordPress is a different beast, in that it's basically saying "YOU WILL CREATE A BLOG or modify this blog and call it something else." Some people like that underlying structure… "okay, we're starting with a blog, what can we do with it?" Others do not like that underlying structure. Our audience consists of those that want to have a system support their original creation rather than mash up an existing creation. There was a PDF posted earlier that I think hit upon some good points, and I appreciate the effort that went into putting it together. The fictional character being scripted in the dialog is not our target. I can go into specifics if anyone wants me to, but I was definitely left feeling at the end of it that we have to be careful about hand-feeding too much or else we'll start attracting people beyond our support resources. Folks that want the fish cooked and filleted rather than folks learning to fish. Perhaps in time we will want to attract more of the consumer-type audience, but currently I don't know how to support users looking to find all the answers in a sitemap file. Keep in mind that unbridled growth is not necessarily desirable. Most of us don't get paid for most of the work we do here and we do best if we grow in a more healthy manner, attracting more thoughtful designer/developers that are here to learn and also contribute. Obviously the author of the PDF is one of the thoughtful ones (and the PDF is a great contribution), even if his fictional character isn't necessarily, but we'll welcome him anyway. But we will definitely be going through the PDF in more detail to learn and improve from it where appropriate, while keeping our audience in mind. I think we're doing something right, because our audience is growing rapidly. I'm nearly full time on ProcessWire now, and it's still difficult to keep up with everyone. At present, I like that our audience is largely open-minded, curious and thoughtful designers and developers. Somehow we've attracted an incredible quality of people and that's what makes this place great. We could not ask for a better group of people here. I'm reluctant to lead PW towards a website builder direction because I think that's when the quality of the community could go down, as people come looking to eat fish rather than learn, catch some fish, and throw some back. The reality is that part of our long term goals include converting the rather large audience that has outgrown WordPress into ProcessWire users. I'm convinced that we do that by giving them more ProcessWire, and not more WordPress. But at the same time, we always have to keep an eye on WordPress and learn. They've been lucky no doubt, but they are also doing many things right. So we have been and always will be working to make the WP-side of users more comfortable in ProcessWire, while also trying to help them grow by distancing them from the limited WP mindset.

I have this same issue when doing one-time migrations of finished sites on my localhost MAMP/dev server (which runs sites off subdirs) to the live server. But the solution is really simple. When I export the database to an SQL dump (via PhpMyAdmin), I drag the resulting SQL file into TextWrangler/BBedit, and perform a search/replace: "/newsite/" => "/". Then I import it to new server (again via PhpMyAdmin). Problem solved on 5 seconds.

Page Link Abstractor is a splendid module, but it also introduces a rather big change to the way PW handles links. If you "just" want a one-time fix for changed links, it might be easier to run a simple SQL query for fields that contain changed links, replacing old links with new ones. Something like "UPDATE field_yourfield SET data = REPLACE(data, 'href="/newsite', 'href="');" should do the trick. Since I'm not sure how familiar you are with MySQL / SQL in general, this may be self-evident to you, but still: a) if you're not absolutely sure about what you're doing, don't try method I mentioned above and b) always make a backup of the table you're working with before making any changes to existing data (CREATE TABLE backup_field_yourfield LIKE field_yourfield; INSERT INTO backup_field_yourfield SELECT * FROM field_yourfield;) By the way, Page Link Abstractors description says that "This module hasn't yet been tested with migrating a site from subdirectory to root, but I will be testing this soon." Old information perhaps?