kongondo

Now I have seen it. Yes, could be a windows issue...see screenshots below Before modesta After modesta @nikola, See Adrian's post above. I also agree with that. Since these new admin themes are modules, they should be able to exists side by side. There shouldn't be any need to uninstall one in order to install/use another ...So, I wouldn't update those instructions just yet... ...Thanks for the theme!

@Adrian, I have the same profile page...but selecting modesta results in the user seeing the very old PW theme instead ...

I was wondering the same but there seems to be a problem. Modesta is selectable on a per user basis but like manfred62 reports, you get the old PW theme instead (old as in pre-admin-theme-as-module old)

Edit 2: Didn't read this properly. You are referring to the modules directory, duh! Sorry! Teppo, you can already do this since a couple of 2.4.1 ago. I can't find the post now but you can specify PHP version and other requirements Edit: Found it: https://processwire.com/talk/topic/778-module-dependencies/?p=56020

Mikael Simply beautiful! I love it!

http://processwire.com/api/variables/pages/ $skyscrapers = $pages->find("template=skyscraper"); foreach($skyscrapers as $s) echo "<li><a href='{$s->url}'>{$s->title}</a></li>";

No. Do not edit MarkupBlog.module. On update, your changes will just be overwritten. In addition, remember, this is a Markup Module; such modules output some markup. The markup has IDs and classes that you can target with your CSS and do whatever you wish. What do you mean by messing things up? What template file are you referring to? Even blog.css is just a demo file. If you are using that, you can delete it or use it as a baseline for your blog. Same goes for pocketgrid.css. Using the example template file blog-post.php (for single posts), to get you up and running quickly, only use the PHP up to line 48. Delete the rest of the HTML below. However, to output the main content of the post, you will need to echo somewhere $content. In that example template file, I have called that variable $content; it could be anything you want. Still on this example, I include the right sidebar stuff using blog-side-bar.inc. You may choose to do it differently. Have a look at the code in there to see how simple it is. My guess is that you are new to PHP? Anyway, try that first and let me know. Are you developing locally or there is a test site I could look at?

Nice addition Ryan, thanks! (Timers)...

Hey, look what the cat's dragged in! Adam, nice to see you!

Franko, Sorry to hear you are having problems implementing Blog. Apologies, I have not had time to write the documentation. It is however quite easy to fit Blog in any design. The reason for the 'many' template files is explained in several posts in this thread . In a nutshell, the many template files have nothing to do with the module; they are only examples, are necessarily verbose and are meant to showcase the methods/functions available within MarkupBlog. Blog is a module and you can call it anywhere, any time you want in your template files. I will write up what its methods do and how to use them when I get some time.

Mosravo A couple of requests/pointers before I attempt an answer If your question does not relate to the specific issue in an existing thread, please start your own topic. This way, the conversation remains clear... Not everybody uses the same templating approach in ProcessWire. Not everybody will know what main.inc is, let alone know what sort of code it contains. Please, be as specific as possible in your questions. I am assuming your are talking about the main.inc in the Blog Profile Please, enclose all code within the code tags provided in the post editor when you are making a post (see the icons) Now that we have the niceties out of the way.. First, I would suggest to test your code in a standalone test page using its own template file rather than something as complicated as the Blog Profile. This way, it might be easier to debug.... Second, your image paths look like this: img src='cssSlider/data1/images/img2013122100548.jpg'. That's definitely not a ProcessWire page image path. Using web developer tools, have you confirmed that the images are actually being served? Are they missing? If not, how are you generating those paths? I am assuming you are not hard coding them, or are you? You have at least two choices with respect to serving the images to your slider plugin: You can create either 1 page with multiple images that you can loop through and output the html that is required by your slider plugin or you can have each image be its own page and loop through them outputting the html the plugin needs. You can save your images in your own folders somewhere in your /site/..e.g. /site/assets/myfolders/ and use PW API to get the relative path to your custom folder and serve your images from there I would go for #1. It will help you to read up on the PW image fieldtype API here: http://processwire.com/api/fieldtypes/images/ Also have a look at the $config API here: http://processwire.com/api/variables/config/ Btw, I don't know about cssSlider but its code looks overly complicated? There's a ton of jQuery slider plugins that would produce much cleaner code...just saying

Oh yes, oops, forgot that. Congrats Germany!

@Diogo...when you come out of hiding , commiserations...Silly Pepe! (but naughty Müller ) .....

Although I would have liked to see England win, for me I was more interested in 'how' England would play. I have never been prouder! So many positives and so many things to hope for for the future. When is the last time you saw England play attacking football and not just sit back? When is the last time you saw England actually bring the ball forward through passing right from the goalie to the front rather than hitting the customary long passes? There's so much to look forward to; well-done lads! Congrats to the Azzurri

Hi Kae, Welcome to the forums! The default ProcessWire install comes with a template file called search.php. It's a demo of search functionality. If you are still learning PHP and hopefully some PW basics too ...I suggest you have a look at that file first and grasp what is going on. As you can see, it is only a few lines of code. You can change a couple of things to suit your needs. If you require more specific help, feel free to post questions

Well done the Dutch! Amazing goals, humble pie for Spain...

If you are comfortable with PHP, with PW you can have your cake and eat it too! I realize I didn't clarify what I meant by the 'basics'...apart from PHP, that's also mainly the 'simple' but powerful PW basic API that is documented here: http://processwire.com/api/ especially selectors, $page and $pages. If you get those under your belt you will be truly on your way. As usual, feel free to ask questions and we'll be here to guide you....

....I was coming to that...OK, let's not kid ourselves, England is not going to win the WC. But, I think our boys will do well this time because there is less fuss this time round around the whole English team, less circus, etc. There's really no expectation on our part. I think the young lads will do us proud nevertheless...they have no past baggage so to speak, are really good players and have nothing to lose. C'mon England!

Aah, this now seems to be a slightly different question. What you are asking is about 'structuring' - the HTML...rather than 'styling'...the CSS, or maybe both? ... How comfortable are you with HTML, CSS, PHP? The first two you definitely need to know, the third you need to know the basics. Answers to this will determine how much re-structuring you can do, especially with the 'work-horse' that is the Blog Profile. If it was just about styling, the place to start is to fire up Firebug (if in FF) or Chrome developer to examine the HTML output of the rendered Blog pages, note the names of the CSS ids and classes and the relevant lines in the CSS files where you need to make changes. Then you can change those as you wish (but you might want to do a back-up of the CSS file first). Ideally, you should be working locally first before uploading to the live site. If on the other hand you want to add things and move things around, you will need to dig into the code. Now, the Blog Profile uses some relatively advanced code and has all sorts of includes coming in from different files some of which also include other files, etc...Unless you are comfortable with PHP and ProcessWire API, I am afraid you will struggle. If you are willing to learn PHP (at least the basics) that is great and will serve you beyond ProcessWire if need be ....So, I can point you to look at main.inc and blog.inc (/site/templates/) since that is where the main magic happens, the former mainly for outputting stuff and the latter the engine room serving different things to main.inc, but it would not help you much if you were not comfortable with PHP and PW API. Having said that, I am not in any way trying to discourage you. I am just recommending that you try and get the PW basics first (if you haven't done so already)...and the road ahead will be less bumpy ....

I think the cup will stay in South America....yes, Messi and co will lift the cup!...OK, there, I said it!

Yes, Brazil didn't play well! Wow; that's a lot of people. Interesting game that one (Spain vs Netherlands) but am sorry, I think Spain will win

OK, ladies & gents. If you are interested in or have been 'forced' to watch football (that's soccer for y'all across the pond)....here's a thread where we can all discuss all matters World Cup 2014 in one place. Predictions, Best, Worst moments, Favourites, Anecdotes...bring it on please!

Roger, Am not sure I follow? What do you mean by 'site guide companies'? Then again, am slow, it's hot outside and all I can think of is the world cup starting in a few hours

Hi Roger, Welcome to ProcessWire and the forums Unless you've edited it, your 404 page is the one titled '404 Page Not Found'. Did you also update your /site/config.php/ file as suggested above?

Something like this should work... $t = $templates->get('basic-page');//get the template $f = $t->fieldgroup->getField('summary', true);//get the field in context of this template $f->description = "This should be the description";//value of the field $fields->saveFieldgroupContext($f, $t->fieldgroup);//save new setting in context Edited for clarity... In this example, we are changing the description of the field 'summary' in the context of the template 'basic-page'.