quickjeff

@macrura I made a post here but maybe you can answer, have a look

https://processwire.com/talk/topic/3057-how-to-keep-pages-organized-when-managing-lots-of-landing-pages/

Any help would be appreciated.

@soma or @evanmcd with this solution and then displaying the vanity url versus the /landing-pages/actual-landing-page-url-here   is this going to affect SEO? Will google crawl the vanity url or the longer tail url?

Thanks. 

@kongondo, good point. Thanks.

@Kongondo -  Okay, cool. I will have to use this for now. I don't think the rest of the module is broken or anything. I think just the loading of the dashboard is buggy. Unless you think I shouldn't run the module on a site that is going to grow at 3-4 posts per week?

@kongondo, that was going to be my plan B.  

@kongondo, It loads but man does it take long. I thought it was going to timeout again. Its just odd, posts, categories settings etc. load lightning fast. 

@ kongondo @adrian - Unfortunately, even adding the limit=10 to all three areas, still loads very slowly. What I don't get is why /admin/blog/posts/ loads so fast and displays all post quickly? Also an FYI, i have 420 posts at the moment. 

I turned on debug and saw that the memory_limit was under what ProcessWire was requiring. 

I am running Mamp and I just increased the memory_limit and the maximum_execution time. I had to crank it to 500M in order for it to work and 60 seconds. 

Is that normal? 

I went back and adjusted ProcessBlog.module $posts to limit=10 and still showing a long load time.

@Adrian, Yup. I was thinking of just taking that approach. It was just for saving time. The Blog Module does a nice job of adding what I needed. 

@adrian even with the limit, the load time is the same.  Almost makes me wonder if I should just hide the view for the dashboard, It doesnt really do much besides give you an overview. I think its more important to show posts. 

Here is the error I am getting now, after I enabled debug:

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 32 bytes) in /Applications/MAMP/htdocs/website/wire/core/WireDatabasePDO.php on line 223

I am running Mamp and I just increased the memory_limit and the maximum_execution time. I had to crank it to 500M in order for it to work and 60 seconds. 

Is that normal? 

It works now, but takes a little while to load with the new settings on the php.ini file. 

So this is where we are with this setup now. 

In the Blog Module by Kongondo

The Blog Dashboard times out, could it be that I imported too many posts? Could it be I installed locally?

Everything else functions like a champ but this part is quite frustrating.

It's actually a fairly odd bug, I can go to /admin/blog/posts and categories, tags, authors, settings, cleanup but the dashboard times out. It will load forever and then fail. :-(

This is after I imported 420 posts using the wordpress migrator.  The posts were migrated correctly and all fields match. Its just an odd bug. Could it be its installed locally? Its very odd. I can go to /admin/blog/posts and categories, tags, authors, settings, cleanup but the dashboard times out. It will load forever and then fail. :-(

Has anyone gotten a slow loading time with a timeout ? When I go to the blog dashboard on a local install, it wont load. In the blog dashboard however, if I go to admin/blog/posts I can see the posts, I can also get to settings, authors etc. but not dashboard. Its very odd. :-(

@adrian Success!!! I have completely migrated a wordpress blog into a ProcessWire site running the Blog module! I will be writing a quick summary and explainer on how to successfully do this. I am sure there are others who are going to encounter this at one point. It will be nice to save a headache and get it done quickly.

@adrian almost there! Had to change the template migrator settings now changing the field settings. Should have it figured out soon.

@adrian I am almost there. Grrrr! I am still messing with the settings of the Wordpress migrator. Although I now have Blog Posts under Posts. :-( hopefully I can figure this out shortly.

@adrian - I tested the solution you recommended and we are almost 100% there. Its very fascinating how the module works. 

After setting up the blog, setting up the migrator and installing the sub module to migrate the posts from WordPress, we have encountered one issue. 

Sure we get all the posts and images and authors etc.  but we get duplicate Templates and not sure why.

Here is what I mean:

We setup style 1 of the blog manager/profile. 

So the tree is like this:

blog/posts/actual-url-to-post

But after the migration, we end up with:

/blog/posts/posts/actual-url-to-post

And none of the posts are in the blog dashboard.

We then can see duplicate templates were created. Posts and Blog Posts but they are different. Once I try to view a post that was imported, it doesn't have view as an option.  So technically, I was thinking of just changing the template to Blog Post(The correct template version, not the duplicate it created)and sure it makes it viewable but it erases all the content. :-(

On import we have tried all the settings, append, overwrite, replace and still no luck. 

Not sure what we are doing wrong. 

Any help would be awesome!

@Adrian, great advice and thank you. I am definitely going to move everything to processwire versus having two systems for one company. I rather have them login once, and control what they need to control. Thanks again!!!!

@adrian, wow this is pretty amazing! I am happy to hear that this may just work better than I thought. With the blog setup and a full site running as well, has anyone done this? If so, how well is it running? The site we are working with is running hundreds of pages in the site and soon ramping to thousands. The blog runs hundreds as well and continuously growing.

Thanks again for everyones great responses and big help! This truly is a bright bunch of developers!

https://github.com/NicoKnoll/MigratorWordpress

I have used it successfully on two new sites and I know Septhiroth has also used it!

So let me ask you this, since the main site is on process wire, how would I import the posts without causing issues with URLs, and the existing page tree?

Hi Guys, thanks for all the feedback.  I will give these solutions a try. 

In regards to the arising questions for using WordPress, yes, I agree. Its NOT my CMS by choice. I actually have steered many away from it. 

The only reason we are still using it is for blogging. The client has multiple posts already and it would be too much of a pain to move away and meet our deadline. Therefore the blog is secondary not the primary application. Trust me, I would love to keep it all under one application.  

Unless someone has a solution for extracting all the posts and links? :-/

Hi Guys, 

We are working on a project which includes a new ProcessWire site and a WordPress blog.  The site is built in ProcessWire and the blog will reside in a directory labeled blog on WordPress (Same Server, Same Root, 2 databases).

Since the Blog should mirror the website, we need to find a way to pass the header and footer to the blog.  This way the user visiting the website will see they have not left the site but is now viewing a blog.  (hope I didn't confuse anyone)  

My question is, has anyone done this?  If so, how?

I have seen others cache the header and footer files from custom CMS's but not on a ProcessWire site. 

Any direction on this would be greatly appreciated. 

Thanks guys!

@Macrura - Good point, already solved my problem! Thanks for the advice. I ended up just building my own template and following ryans advice.  Was able to create an array that pin points the hidden pages I want included in the sitemap. 

I have installed this module however, I have some pages that are hidden from the navigation, in which I still want them added to the sitemap. I have added a checkbox field called sitemap.  This field allows the user to add to the /sitemap page.

Here is what I use for the sitemap template:

foreach($page->children("include=hidden, sitemap=1") as $child) sitemapListPage($child); 

I need to do the same thing but for the sitemap module. I am having some trouble accomplishing this. Any help would be great.