jbx
Forum Replies Created
-
Yep, its even in the Widget API tutorial here.
It won’t do any harm, because whoever doesn’t have any title filters won’t see any difference.
Yeah, I already modified it for my case to work.
Just wanted to let you know about it for a possible future fix.
cheers
Oh, it works now. Thanks!
You might want to fix the
theme-3that comes with the default installation in your next release, because it uses$theme_options['subject']so someone following it as an example will get it wrong.Hi Stefano,
I just upgraded to version 3.1.1 and tried this again and I am still getting ‘Here is the email subject’.
In my theme I have this line to test it out:
$theme_options[‘subject’] = “Weekly Update”;
But it isn’t having any effect.
Sure of course. Thanks!
@srijith.v I see the code was included in the latest 3.0.3 release :). I can finally upgrade, thanks… will try it out tonight.
Hi Stefano,
OK I will try to play a little with .htaccess and see if I manage to redirect to ~/subscribe when ~/newsletter is invoked without URL pamameters.
The problem with the current one is that the subscribe form generated by the plugin is read-only, so I cant fix it to look like the other one.
If you want, it would be nice to add an optional ‘subscribe’ URL (just like the current ‘newsletter’ URL configuration) so that it redirects to it if it has it set. Maybe you would like to consider adding it in a future release of Newsletter.
Thanks again.
OK thanks.
When do you think you’ll be releasing the new version?Sorry to bump this, any idea why I can’t override the subject in my theme?
Cheers 🙂
You should notice that in the WYSIWYG editor when you click on the text itself the Link icons get activated, which means they have a link.
Glad it worked for you too.
Forum: Plugins
In reply to: [Attachments] Attachments not working on certain content types after upgradeOK dude, no worries.
Users who get stuck have this post to help them too :).Forum: Plugins
In reply to: [Attachments] Attachments not working on certain content types after upgradeHey Jonathan, thanks for replying!
Re 2, understood. I had upgraded Attachments to v3 and migrated before I upgraded wordpress to v3.5, so I probably left everything default especially since the purpose of custom instances seems to be custom fields.
Can you clarify if once you migrate, and all the attachments with the current posts are associated with the default ‘attachment’ instance, can they be moved (after migration) to another instance? When I tried to add another instance the attachments I already had (which were migrated automatically) remained attached with the old one, and the new instance just displayed another widget underneath (in the edit post screen). I was afraid to disable the default instance because the blog’s attachments would disappear.
Re 1 and 4, I don’t completely agree with the approach though. Custom content types could come from our own plugins, but more often than not, people install other plugins. In this particular example I was using a custom content type from Events Manager which is brilliant, just like Attachments plugin is. It would have taken me ages to develop an events manager myself to just have attachments to events.
The only issue here is that before (in v1) it used to work with all content types, and after upgrade the attachments edit field disappeared. It gave me quite a scare 🙂 but in the end I managed to piece things together. Maybe the migration script (for people who havent yet upgraded), could take care of checking which content types v1 is currently associated with so that the upgrade is at least backward compatible. I got even more confused because when I upgraded Attachments v3 remained working fine (due to the deprecated v1 branch), and then when I upgraded wordpress itself the problem occurred, which threw me completely off because it was working fine with v3.
I had the same issue. Instead of
the_excerpt()useecho get_the_excerpt()and if you want to wrap it in a<p>or anything do it manually. For some reason the HTML code generated bythe_excerpt()interferes (I didn’t investigate thoroughly what is actually happening, but the solution worked).The issue was actually with the Attachments plugin. After they upgraded it to work with the latest WordPress 3.5 features they decided that by default it only works with posts and pages content types. You have to mess with PHP code in your functions.php to get it to work with other content types.
More details here for anyone who faces the same issue:
http://wordpress.org/support/topic/attachments-not-working-on-certain-content-types-after-upgrade?replies=2
Forum: Plugins
In reply to: [Attachments] Attachments not working on certain content types after upgradeOK, so after doing some piecing up of information I managed to fix this, although the documentation is not that clear (might be useful to update the doc). These are the things I deduced, would appreciate if I get a confirmation that I didn’t mess something up without knowing.
1. The new Attachments (v3) plugin by default only works on ‘posts’ and ‘pages’. So the moment you upgrade, other content types (such as ‘events’ from the Events Manager plugin) will not offer you the facility to add/update attachments from the edit screen.
It would have been more intuitive if there was a simple settings screen where one could select the content types to be mapped to the default instance (rather than messing up with PHP code).
2. When you upgrade from v1 to v3, all the images attached to the current posts and content types will go to the default ‘attachments’ instance. It is not clear whether they can be moved to another instance.
3. If you add your own instance settings as described in the doc, you will end up with 2 instances on the main posts and pages, and one instance on the custom post types (which I don’t want because the old attachments are now on the default ‘attachments’ while the new attachments will be on the new one). However, it seems that if I name my own instance ‘attachments’ the settings I pass override (or merge with? no idea) the default ones.
Also watch out for the mistake in the PHP code in the first line of the function given in the example. Should be:
$fields = array(
not$fields => array(.4. You have to know your content type names to put them in the PHP code. (No idea why it was assumed that we would know the actual internal names of content types of plugins we install, a settings screen with the list of content types would have helped!). I happened to have a plugin Custom Content Types installed, which lists them all, so I could copy their names and put them in my functions.php.