barkgj
Forum Replies Created
-
Forum: Plugins
In reply to: [MapPress Maps for WordPress] Oops! Something went wrongI created 2 support videos that show the process of signing up for the proper key at Google here, hope those can help you out; http://oopssomethingwentwrong.com/ (vids are at the bottom).
Forum: Themes and Templates
In reply to: How To Remove Links In Footer?Hi,
Wouldn’t recommend the CSS approach; it generated a cloaked link, and also is not guaranteed to work if an update is made on the theme. Would recommend you to follow the instructions as seen on the Youtube support video (linked from the FAQ of the website of NexusThemes);
Instruction;
1) open the site settings
2) click on “header footer”
3) adjust the footer link to your needs (use a space (” “) to remove the link, or enter HTML to replace the default)Forum: Plugins
In reply to: [WP Ultimate Recipe] Incorrect shortcodeOk, I managed to display the recipe 🙂 Thanks for your quick follow-up, great stuff.
Forum: Plugins
In reply to: [WP Ultimate Recipe] Incorrect shortcodeO, I figured it out; its not really a shortcode, but hard coded in the plugin as a replace… ok, *bummer*. Any reason why not simply use a shortcode there?
GJForum: Plugins
In reply to: [WP Ultimate Recipe] Incorrect shortcodeHi, ok, excuse me but where exactly is the add_shortcode defined for the “recipe” shortcode? I couldn’t find it anywhere, and in our site the shortcode is not being rendered (where-as the shortcode for ultimate-recipe is), so I must be missing something here… Could you pinpoint me to the right direction?
Thanks!
GJForum: Plugins
In reply to: [Custom Content Shortcode] Video links are not converted to embedded contentActually I created a video yesterday here that explains how we use the plugin and [content] shortcode, in combination with the front-end editing. See the video here. For other video’s check our support section. Let me know if you would like to use one of our themes, I can provide you one for free if you would be interested to see how it works 🙂
Forum: Plugins
In reply to: [Custom Content Shortcode] Video links are not converted to embedded contentI didn’t even know that replacing the video links was a feature of WP, but a client of us informed me that the embedded video’s didn’t show up (and I was using the [content] shortcode. Thus, my advise would be to have this be the default behaviour (as you suggested) for posts (but I would do the same for pages, as I am 99% sure WP does the same for pages).
In this way your plugin would behave in the same was as WP does by default, which is I think what you try to accomplish. Optionally, you could make it not do the autoembedding, by using a parameters in the shortcode, like [content autoembed=’false’] or so.
Just in case you are wondering; we have created a front-end editor, and I use your plugin to position/place the WP “backend” content (postcontent) in draggable locations and thus would like the behaviour of [content] to be 1:1 with the behaviour of normal output of WP.
Thanks!
Cool, thanks Eliot!
Forum: Plugins
In reply to: [WordPress MU Domain Mapping] WP 3.6 outputs NOTICE warnings ESCAPEOk thanks for your feedback all, I guess I can then mark the issue as resolved.
Forum: Plugins
In reply to: [WordPress MU Domain Mapping] WP 3.6 outputs NOTICE warnings ESCAPETrue, but the downside of that approach is you also wont be able to see debug messages generated by other plugins / themes. Debugging lines _can_ be practical, unless they are not, like the one generated by sunrise.php 😉
Forum: Plugins
In reply to: [WordPress MU Domain Mapping] WP 3.6 outputs NOTICE warnings ESCAPEFor those who experience the problem here and looking for a solution, do a ob_clean invocation in the functions.php of your theme to clean the notice generated by sunrise.php. Worked for me 🙂
I concluded myself there could be several directions to solve this problem:
a) requesting NextGen to _do_ inject the redirect.php file. I concluded this would not be ideal; other users would be ‘punished’ with more heavy memory load even though for them this would not add any benefits. I also concluded this solution would not help our theme in a proper way as other plugins might use the same optimization techniques so I would have to repeat these steps for each other plugin working the same way.
b) forking NextGen and adding the redirect.php. I condluded this would also not be ideal; each time a new version of NextGen is released we would have to make another release of the fork too. Would be too time consuming. Also this approach would require end users to have to perform actions to ‘solve’ this problem, which is not very user friendly.
c) inkecting a non-standard webservice implementation in our WP theme that does a 1:1 copy of the “original” WP webservice implementation, without defining the DOING_AJAX. This sounds like the best approach; end users don’t have to do a thing to have NextGen work using our theme, and NextGen doesn’t have to adjust anything.
Closing the task 🙂