I have a patch which I want to close and hide in my project without landing it myself or let others to land it later on. This patch is just obsolete.
Is there any way to close/delete/reject this? I think so, because on their website it says:
You can reject code if you don't like it.
You can use the "Abandon" option in the "Add Comment" section to close revisions you no longer intend to pursue.
Use the "Abandon" option in the "Add comment" section at the bottom of the page.
Related
So I want to enable CloudFlares Rocketloader feature on my site as it significantly improves the load times of my page.
Thing is, the Add to Cart button doesn't load when it's enabled.
The CloudFlare documentation states:
"You can have Rocket Loader ignore individual scripts by adding the
data-cfasync="false" attribute to the relevant script tag"
I think I need to add the above code to the correct script but I have no idea what the script is called or where it is.
Any help would be greatly appreciated. Thanks
The ignore option doesn't always work (kind of complex). Is it just happening on a specific URL, such as yoursite.com/checkout? If yes, then you might want to look at turning off Rocket Loader on that URL with a PageRule.
I was able to find the function that sends an email every time a new item is created. Unfortunately I lost my notes and I can not find this feature more. Remember, that you entered the menu zope them and outlined a function to the occurrence of an event ..... can you help? Sorry for the bad English,
thanks.
You simply need to use a Plone native feature: content rules.
Go the the "content rule" section of your Plone control panel (http://yoursite/##rules-controlpanel) then configure a rule with a "mailer" action. The trigger action could be a workflow transition change.
My completely finished website started displaying "region" in all the regions instead of the content. This was shortly after I enabled "Calendar Multiday" so perhaps it was related (although I have now disabled that module). Calendar and Date were previously enabled and working perfectly. I am not actually sure if the problem has anything to do with the module.
Anyone seen anything like this? Could it have to do with access control? I disabled the module but that didn't do anything..
To be clear, even admins cannot see the content and simply see "region" in every region.
please clear the cache and tell me if its solved the problem... you can clear the cache by flushing the database tables that start with cache_... , or by implementing cache_clear_all(), drupal_flush_all_caches() functions ...
Check the region.tpl.php file if you have this problem as it was overriding all my content!
I've noticed there is one more tab in my edit-content pages in Drupal.
Could you tell me which plugin added it ?
See picture: http://dl.dropbox.com/u/72686/TrackTab.png
I actually need to know step by step how can I disable such tab
thanks
besides tracker.module (and, as mingos said, possibly other contrib modules), a "Track" tab is also added (to nodes) by statistics.module, statistics_menu().
UPDATE: this tab is only visible to users with "access statistics" permissions, so just adjust your site's permissions accordingly. as user #1 you will always see it, though.
you can, of course, just disable statistics.module.
Either Tracker (core module) or Tracker 2 (add-on) adds such a tab, but I've noticed it only on user profile pages.
I really like how Lifehacker.com (and Gawker.com) implements their comment system.
I believe, but am not certain, they use Movable Type as the platform for their blog.
What I like about their comment system is that it's a simple open text field and once you click "Share" it then asks you to register.
Question: Anyone know how to accomplish this same functionality with either Wordpress or Movable Type?
The Gawker blogging network (of which lifehacker and gizmodo are part) use their own custom blogging platform (Pingdom blog post at beginning of last year)
If you want users to register before they leave comments, go to Admin > Options > General and check "users must register to leave comments" (or at least I think that's the right path, I'm doing it from memory)