webdesignby

I have verified that is the only solution. You must create new site keys.

Unfortunately there is no elegant workaround that I can find to test for this condition and allow you to still log into the wp-admin without compromising the security purpose of the plugin.

Hi,

Yes there is a musicbox shortcode you can use with the following parameters:.

• musicbox_id * required value: the id of the musicbox to display
• description optional value: whether to display description or not. “1” or “0”, default is “0”.
• autoplay optional value: whether to autoplay list or not. “1” or “0”, default is “0”.
• tracks_perpage optional value: how many tracks to show before paginating. Numeric value. Default is “10”.

Ex.
[musicbox musicbox_id="1" description="1" autoplay="1" tracks_perpage="2"]

I should add this to the documentation.

Please give the plugin a review. Thx for using and asking.

resolved

I figured this issue was important enough to address right away. I have pushed an update to address the enter key behavior. You can update now in wp-admin.

I did some testing. Try clicking the lookup button instead of pressing enter. I will address this issue in the next update so you will be able to use the Enter key.

Hey sorry for the late check-in. I am not sure how to activate Email notifications in this system. Glad you were able to quickly figure it out.

Hi mia, no worries ??

I fixed my issue by changing the owner of sitemap.xml and sitemap.xml.gz then manually rebuilding…

chown apache:apache sitemap.xml.gz
 chown apache:apache sitemap.xml

I am not sure what your issue could be…

Do you see any warnings in your WP Admin under settings -> XML-Sitemap?

Hi,

Some more details to recreate my issue.

I am using a manual excerpt in the excerpt field for my posts.

In my loop I am using the following code:

if (function_exists('has_excerpt') && has_excerpt()) the_excerpt();
   					else the_content('Read on...');

So the issue I am having is with the manual excerpts and this code used to display the excerpt when present.

Thank you,
Ross

Never mind. I got it. Magento and WordPress do NOT have to be using the same database.

My issue was I did not have

if(class_exists('Mage')){
    Mage::getSingleton('core/session', array('name' => 'frontend'));
 }

above get_header(); in my template file.

Great plug-in. Thanks!

Restart MAMP effectively addresses the issue.

Exact same as above….

numeeja – I think a percentage of them could be just sniffing around.

esmi – Thank you for the informative reply. This helps me understand possible legitimate motives for people registering. I will continue growing my content and who knows, maybe some day I will offer something interesting to my subscribers.