craigf136

Please, please, please, please re-add the ability to export templates without a database. Lack of premade MP templates for the articles database, including feed block templates, is directly related to Pages requiring we export the entire database, which makes absolutely no sense for the database that is preinstalled, and doesn't actually work for it, and that's not even considering the point that block templates cannot be exported via any means.
Those of us that can code cannot help those that cannot premade in this area with the way it is now. I cannot even do a custom locally with the way it is now, as there is no way to transfer such, which ends up with me working on a live site. Not cool. I was actually waiting for a topic such as this to be made. If somebody with a basic clue and can code like myself is struggling due to this, I can't imagine how painful this is for the layman, and the surprised look from staff was not expected... I put in a feedback topic a while ago begging for this to be restored, and have left it since then, but it is a very real need.

Thanks for the feedback, Danny. 
You are certainly right about the documentation. Pages has it’s own structure and logic of modules and without proper documentation it can be be a struggle to understand it and get good results. 
But I also disagree about some points. 
Wizards and Template: If you add a page, a database, a field, a menu, … – you will get wizards which guide you through the setup. Templates are now easier than ever, since you just open the page builder and drag & drop everything wherever you want to. That was impossible in 3.4, where the slightest layout change would require coding. Not anymore! Customization. Customization requires custom code. That’s just in the nature of things. The look of WordPress posts/pages is defined in template/CSS files and if you want to make even little changes, you would have to make code changes. That’s just the way it is. More user options alone won’t change this. I would even say that Pages offers more choices than those other CMS. In WordPress you can only define the position of sidebar widgets through drag & drop, in Pages you can do that for the whole page and for every page individually. 
Another improvement in 4.0 is the field output, which is now controlled directly in the field settings, again helping you NOT to touch the page templates. Most other standard content management systems don’t even have custom fields as a stock options. And lastly, where are those “tons” of forum questions about Pages with 0 replies? If the questions are understandable and can be answered with reasonable effort, I keep answering them for months. 

Thank you for taking the time to share your feedback. Pre-made templates are something we'd like to do. We'd also like to release our own work we've done here for examples to use. 
You may find the improvements being made to Pages in a soon-ish release to be of more help to you. Finally, we have a number of tutorials done and on the way that are being reviewed internally. Hopefully all of these combined will maximize the benefit of the product to you. 
Thank you again.

Can I have acp access to this forum? Seems weird it would limit the amount of options available.

@Gabrielle V. we had some issues today and our site went down when removing plugins. The site came back online thanks to IPS Support, however the forum topics and posts would not appear. The topic and posts could not be accessed a blank page would be displayed - upon checking the error logs the following was identified.
[12-Apr-2015 21:59:32 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:02:57 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:03:06 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:03:16 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:03:58 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:04:53 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:05:58 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:06:05 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 [12-Apr-2015 22:06:08 UTC] PHP Fatal error: Method IPS\Content\ShareServices\Whatsappcvh::__toString() must not throw an exception in /public_html/system/Theme/Theme.php(624) : eval()'d code on line 0 Disabling the file in /system/content/shareservice/ immediately resolved the issue, I'm not saying this was the root cause of the issue but it was a contributing factor.

 

​Although not an issue for me, it may be beneficial to include it as standard and prevent unnecessary support topics/posts regarding it

@craigf136 or go to ACP -> Customization -> Themes -> click < / > button on right of your theme -> featuredcontent -> manage -> itemRows
Find
                    <a href='#' data-ipsdialog='' data-ipsDialog-url="{url="app=featuredcontent&module=slider&controller=view&do=manageSlider&id={$Slider->id}&item={$row['id']}"}" data-ipsdialog-size='narrow' data-ipsdialog-title='{lang="fcs_edit"}' data-ipsdialog-forcereload='true'>                         <img src="{$row['image']}" alt='' style="width: 100%; height: 150px; cursor: move;" title="{$row['title']}">                     </a>                     <span>{$row['title']}</span>Replace with
<a href='#' data-ipsdialog='' data-ipsDialog-url="{url="app=featuredcontent&module=slider&controller=view&do=manageSlider&id={$Slider->id}&item={$row['id']}"}" data-ipsdialog-size='narrow' data-ipsdialog-title='{lang="fcs_edit"}' data-ipsdialog-forcereload='true'> <img src="{$row['image']}" alt='' style="width: 100%; height: 150px; cursor: move;" title="{$row['title']}"> <span>{$row['title']}</span> </a>Save

Okay, finally I can reply.
This plugin would not have caused issues with memcached but, yes, at the time it would have caused issues after having disabled via plugin rather than System > WhatsApp > Sharing.
I've released version 1.0.4 which completely changes how this plugin functions so this issue should be resolved.

​That issue is generally caused by a missing template. There is an IN_DEV specific template (which is uploaded to /applications/core/dev/html/front/sharelinks/whatsapp_cvh.phtml) and then there's the one saved by IPS when installing the plugin. 
I'll make a note in the zip of how to uninstall the plugin correctly (which, yes, you have to delete the physical file in /system/content/shareservice before uninstalling the plugin).
Thank you for bringing this to my attention and I'm sorry it caused you issue. :/
edit: I have some ideas how to make this a non-issue in the future (by somehow piggy-backing on a hook).

​ECA's = Events, Conditions, Actions
I've built the rules framework to be entirely extensible by 3rd party applications. Rules includes "core" ECA's for things that all apps will have in common, but any specialty ECA's for 3rd party apps can be provided as an IPS extension to my rules app right inside the 3rd party app. And if the 3rd party app developer doesn't want to include ECA definitions for compatibility with rules, then myself or another developer could easily create an expansion plugin specifically for that 3rd party app to add ECA's to rules. Either way is fairly easy with the framework I've built.
Note For Developers: If you want to add any rules ECA's to your app ( beyond what rules will already provide ) and give users greater power over your app, then all you need to do is add a rules extension to your app from the developer center (you must first have the rules app installed to your dev site). The extension template that is added to your app will be well documented. I will also provide additional standalone documentation very soon.

​The problem with core IPS pips is that they are not saved anywhere for members individually, and are manifested using on the fly calculations. In order to control them conditionally, a rule would need to be inserted into the calculation every time a pip displays on the page. It's not an ideal application for rules.
But that doesn't mean you can't get the job done with rules. You could use rules to either supplement or even replace the core pips feature entirely with your own. Here's one way to do it:
Create a new integer field attached to members via the rules ACP, and call it "Pips Rank" or something. Create a custom action in rules and call it "Update pips rank", or something to that effect. Create a single argument for the action... a member object. Create a rule set to contain your rules for this particular functionality, call it "Custom Pips System", etc. Add a rule to the "custom pips system" that is triggered when new content is created. Add an action to that rule that triggers your custom action: "Update pips rank". Add another rule to the "custom pips system" that is triggered when reputation is given. Add an action to that rule that triggers your custom action: "Update pips rank". Now add a rule to the "custom pips system" that is evaluated when you trigger your custom action: "Update pips rank". Let's call it "Update member to the appropriate pip rank". At this point, you now have a custom action that is being triggered every time someone either makes a new post, or receives reputation on your system. You have also created a rule that is going to be evaluated when that custom action is triggered. All that's left is to create a rule group that saves the appropriate value to the "Pips Rank" integer field for the member based on your own criteria.
Example sub-rules (for your "Update member to the appropriate pip rank" rule):
Subrule #1
 Subrule #2
Etc, etc.
Conclusion
There you have it. That's a complete replacement system for the IPS member rank system. In the end, it consists of a: custom data field, custom action, two rules, and a rule group to control the pips promotions.
The last piece of the puzzle is how to actually display your "Pips Rank" on the front end. That would require a small theme template edit. You could add the following template code anywhere you wanted to display the pips ( assuming the $member object is available in the template ).
{expression="str_repeat( '<span class=\'ipsPip\'></span>', intval( $member->getRulesData( 'pips_rank' ) ) )"} 
I've taken the liberty to create this system in rules and I've uploaded it to the marketplace. Feel free to download it from there.
Download Member Pip Ranks System

I bought it, it looks extremely beneficial with many usages available (to many to list). I think it could do with a few example rule sets already implemented though, I have many that I could think off but I'll have a play around and see what I can do myself and what I may need assistance with.
Kudos due on a superb application.

If this is your first time doing something like this or not confident, it is always a good idea to make a backup of both your database and files that are in production. Just in case you make a boo-boo. Better to have it and not need it than need it and not have it  

How I did it.
download copy of config.php from live site login to cpanel and create a new database IPSV4b5 for example Assign existing user to the database create directory / subdomain for the test install (remember that this is the URL that will be used for all test installs Upload the files for IPB v4 copy public and upload folders for live site (don't move, download locally - you could also compress these two folders and move the compressed file and then extract that by using cpanel file manager) then upload them to the directory for the test install (I personally took it offline for maintenance for 5 minutes). You can do this part in one of 2 ways, take live forum offline or leave live (crude but effective) change the upload paths to the uploads paths for the test database you can also do this via phpmyadmin but I'm not 100 certain on what needs changed in the database but only do it once you have copied the database (see below) login to phpmyadmin, go to existing database, and then select operations,
Untick create database before copying and in the field above, enter the database information and then click go to copy the database to the test install database once it has copied, go to the config.php in the test install directory edit and enter the test database information (replacing the live database information). then go to www.domain.com/admin/upgrade and run the upgrader, it will ask you to convert to UTF8 if you haven't already done so. Follow the upgrade steps