ExpressionEngine Community Forums

SL Freshview Subscribe v1.4.0 : Now fully compatible with Solspace’s User module

2008-09-19T07:03:38-06:00

Version 1.4.0 : Release 28th July, 2009
* Implemented support for User module on sites that don’t require member activation.
* Added bash script to create symlinks.
* Fixed a minor JavaScript bug, when displaying the available values for a custom member field of type “Drop-down”
* Fixed a silly error introduced in the previous version, that was affecting simultaneous subscriptions to multiple mailing lists.

Version 1.3.1 : Released 16th July, 2009
* Implemented handy drop-down list of available values for all custom profile fields of type “Drop-down List”.

Version 1.3.0 : Released 16th July, 2009
* Implemented workaround for LG Addon Updater bug.
* Moved assets to sl_freshview_subscribe folder within extensions

Version 1.2.2 : Released 27th May, 2009
* Minor tweak to make everything play nicely with PHP4.

Version 1.2.1 : Released 12th May, 2009
* Fixed bug related to CampaignMonitor accounts containing a single Client, or a single List.
* Improved error messages.

Version 1.2.0 : Released 22nd April, 2009
* Added support for sites that don’t require member self-activation via email (as set on the Membership Preferences screen). The extension automatically detects the membership preferences, and takes the appropriate action.
* Implemented a “Disable Extension” button in the top-right of the extension settings screen.

Version 1.1.0 : Released 14th April, 2009
* Implemented full support for custom fields on a list-by-list basis.
* Custom Profile Fields now appear as a drop-down list, instead of an uninviting text field.
* Underlying code completely rewritten. All the API querying is now handled by PHP—meaning we can kiss goodbye to the JavaScript-PHP proxy file nonsense—and CampaignMonitor’s PHP “helper” class is used for all the donkey-work.
* Moved minimal remaining CSS and JavaScript out of separate files.
* Far too many little improvements and tweaks to list.
* Oh yes, and finally got around to adding a change log.

—-

Hello all,

SL Freshview Subscribe makes it easy to subscribe new members of your ExpressionEngine-powered website to one or more CampaignMonitor mailing lists. Here are a few of the highlights:

* Automatically add a member to one or more mandatory mailing lists.
* Specify “opt-in triggers” to allow a member to control which lists he is added to.
* Associate custom ExpressionEngine member profile fields with custom CampaignMonitor fields on a list-by-list basis.

Simply enter your CampaignMonitor API key, configure your mailing lists, and the extension does the rest.

You can download the extension from my site, which also includes full installation and usage instructions.

Support is provided via this thread.

Cheers,
Stephen

New Extension: Show Categories on Edit Page

2009-04-24T05:51:12-06:00

Hi all, so I got fed up with waiting for someone else to do it and wrote a little extension to add a column to the edit page which shows the category assignment of entries. Obviously entries can often have numerous categories so there’s a setting to configure a display limit and when this is in use additional categories will be displayed when hovering over the primary category for that entry (via the abbr tag).

This is my first extension that interacts with the edit page so I’m not sure whether it’s possible to control the placement of the extra column or not, it’s current location at the end of the row is not ideal… if anyone knows of a way to adjust that or whether it’s possible to add more than one column to the edit table at a time, let me know!

http://ninefour.co.uk/files/labs/nf.show_categories_.ee_addon_.zip

Finally, I should mention that I used the md_weegee extension as a starting point in developing this so some kudos there to Ryan for his extension that provided me with the building blocks for this.

New extension: EEvent Helper

2009-09-18T18:49:41-06:00

Hey all - I wrote this extension today after being frustrated yet again at the tedious instructions I aways have to give my clients when posting to an “events” weblog in EE. Telling them to manually set the Expiration Date so events disappear when they should; having them set a separate end date for multi-day events, which is located in a totally different spot than the entry date in the Date tab ... not so slick.

This extension has solved these problems for me completely, and I was so stoked with the results that I implemented it on two older sites right after I finished it for the current site I’m working on. Hopefully someone else can find it as useful.

Once activiated, when entries are published in your specified “events” weblogs, their Expiration Date will be automatically set to 23:59:59 on the day of the event. Or, if you choose a custom date field to serve as an End Date indicator, their Expiration Date will be automatically set to 23:59:59 on the End Date (if it’s not empty).

You can also specify a custom Start Date field to use instead of the Entry Date calendar from the Date tab. Once you specify this field, you can automatically set the Entry Date to match the custom Start Date field, eliminating the need for the Date tab altogether. This way, you and your clients can use friendlier custom date fields for both start and end dates, while always keeping the entry’s Entry Date and Expiration Date set properly for use in exp:weblog:entries tag parameters.

Lastly, you can force the Start Date and End Date fields to have their time set to 00:00:00 upon publishing.

Note that only fields of the built-in ExpressionEngine “Date” fieldtype can be selected as Start Date or End Date fields.

EEvent Helper has been tested on ExpressionEngine 1.6.8.

UPDATE: - version 1.0.1 includes the option to hide the date localization toggle on the custom date fields, and choose what the default should be.

UPDATE: - version 1.0.2 updates the “force midnight” setting to also remove the “time” portion of the date fields in your Events weblog, so the calendar picker inserts dates in the format of YYYY-MM-DD. The time will still be automatically set to midnight when published.

UPDATE: - version 1.1 supports settings for multiple events weblogs. EEvent Helper also now requires CP jQuery loading jQuery 1.3+.

UPDATE: - version 1.2 is more MSM-aware (previous versions worked with the MSM, but version 1.2 is optimized for it).

Download it on GitHub.

MX Universal Editor - integrate TinyMCE / MarkItUp /CKEditor with FileManager and LinkManager support; Updated 10Feb10

2009-10-09T07:35:23-06:00

last update in this post

Hello,
MX Universal Editor extension is the next version of MX TinyBrowser. I decided to rename it for better understanding functionality of this extension. Documents are not finalized yet, so for beginning a short introduction.

What it is? (you can look at screenshots)
MX UniEditor is Fieldframe field and helps you to integrate TinyMCE/CKeditor/MarkItUp with FileManager and LinkManager support into ExpressionEngine as a piece of cake. And more - you can integrate FileManager as standalone custom field (like File or n-gen file ext.).

And remember – if you will have any issue or bugs, feel free to send me a note and I will help you ASAP.

Working on…
Amazone S3 support
Uploadify standalone field with cropping
Working on new TinyBrowsed functionality and usability

screencast
screenshots
download
previous version (MX TinyBrowser)

New Extension: Seesaw

2009-12-20T17:13:56-06:00

Seesaw allows you to configure the Edit Channel Entries page to show/hide columns on a channel-by-channel basis.

Updated to 0.4.9. Please see below.

The premise is simple:

For the default view, when all available channels are displayed, Seesaw allows you to show/hide the “core” columns (ID through Status).

If you then filter the list with the search form so as to limit results to only one channel, Seesaw allows you to show/hide any custom fields assigned to that channel.

This works great with the Edit Menu and Edit Tab AJAX, and early tests indicate it plays nice with other add-ons that modify the Edit table (Weegee, Cloner, Live Look, etc).

Similar Plugins:

This has been approached before, I’m just taking a slightly different angle. But it’s worth giving a nod to those who came before me:

- NB Show Custom Field Data
- Edit Custom Field By Label
- Simplify Edit Table

Installation:

1. Copy lang.seesaw.php into /system/language/english/
2. Copy ext.seesaw.php into /system/extensions/
3. Enable the extension via the Extensions Manager (Admin > Utilities > Extensions Manager)
4. Visit the Seesaw settings page to configure the various Channel views

Upgrading:

Simply overwrite extension & language files.

Type/Format Configuration:

text (char limit):
Select this option to limit the field output to a certain number of characters. Enter that limit count into the “format” field, e.g. “30” (without quotes). If no value is given, the entire field will be output.

timestamp:
Select this option to convert a timestamp into a human-readable format. Enter the format string into the “format” field, e.g. “%y %m %d” (w/out quotes).

MX UniEditor Img (NEW):
Supports Max Lazar’s MX UniEditor Img extension, showing thumbnail. No format value required.

Custom HTML (NEW):
Allows to freely format field as desired using HTML. Use “{value}” (without the quotes) to access field value, e.g. “<em>{value}</em>”

Requirements:

Seesaw was built on ExpressionEngine 1.6.8, though it uses hooks available since 1.4.0. If you manage to install it successfully below 1.6.8, please let me know.

Changelog:

0.4.9
- Support for PHP4
- Rebuilt column replacement to be less destructive. Initially to play nicer with Edit Table Plus, but should benefit others too

0.4.8
- Added Gypsy compatibility

0.4.7
- Fix compatibility with Webee Quick
- Avoid notices thrown when Brandon Kelly’s Gypsy extension is in use
- Fix call to LG addons (hopefully)
- Fix php4 construct method name

0.4.6
- Complete support for LG Addon Updater
- Add support for custom_html
- Add support for MX UniEditor Img
- Improve input scrubbing & prep for DB insertion
- Bug Fix: See forum post

Possible Upcoming Features:

- Add an nGen File Field type (show as thumbnail)
- Add a URL format field
- Add FF Matrix support
- Add Playa support
- Allow for all Channel views to inherit Defaults
- Allow to show other “core” fields, e.g. expiration_date

nGen file uploads bomb out when larger than 3MB or so?

2010-03-15T14:15:42-06:00

Has anyone else encountered an issue with nGen and file sizes?

We’re running a MSM site and uploads over 3MB or so bomb out when uploading. We are using nGen File Field 1.0.

The error we get is:

“Something happened while uploading (filname) Please try again”

We were on an earlier version before upgrading nGen to 1.0 and got an error, although not as pretty as the one in 1.0:

Warning: getimagesize() [function.getimagesize]: Filename cannot be empty in /home/(directory)/public_html/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php on line 10

Warning: Cannot modify header information - headers already sent by (output started at /home/(directory)/public_html/admin/extensions/fieldtypes/ngen_file_field/ft.ngen_file_field.php:10) in /home/(directory)/public_html/admin/core/core.functions.php on line 296

Extension: Weblog Rights

2010-02-22T09:10:25-06:00

There is a quite popular feature request - to allow membership in multiple groups. One of the main reasons for such feature is the need to have more power in assigning weblogs to users.
For example, if you have 3 weblogs - A, B and C - and need to allow some users to post into A, some others - into B, yet some others into C, yet some others into A and B, yet some others into A and C etc., then for managing weblog permissions you need a lot of member groups. To be exact, if you have number N of weblogs, you may need

2<sup>N</sup> - 1

member groups.

To solve the problem of too many member groups I created Weblog Rights extension. It allows you to assign weblogs on per-member basis. So, for managing weblog permissions of the above example you will need only 1 member group.

Unfortunately, for this extension to work a hack is needed.

In /system/core/core.functions.php
around line: 1195 (inside function fetch_assigned_weblogs($all_sites = FALSE) )

find:


return array_values($allowed_blogs);

Replace it with:

// -------------------------------------------
// 'assigned_weblogs_array' hook.
//  - Exclude/Include weblogs in the asigned weblogs array.
//
global $EXT; 
if ($EXT->active_hook('assigned_weblogs_array') === TRUE)
{
 $allowed_blogs = $EXT->call_extension('assigned_weblogs_array', $allowed_blogs);
}

return array_values($allowed_blogs); 

New Extension Template (1.6.x)

2010-03-19T18:58:16-06:00

I freaking hate needing to start extensions from scratch every time, and I haven’t developed enough of them to have a solid library of extension snippets. I finally bit the bullet, and coded a new extension template to jump-start the custom extensions that I need to create for clients. You can find the template attached to this post, and usage instructions are in comments near the top of the file.

This sucker is heavily based off Leevi Graham’s free extensions, and released under the same license. Thanks Leevi! You’re awesome.

Hopefully others find it useful, and if you figure out a great way to improve it please consider sharing.

New extension: Entry REEdirect

2009-10-01T13:03:17-06:00

My clients often get confused by the “preview” screen they come to after publishing or updating entries. Frankly, I do too. So here’s a fix for that.

Entry REEdirect is an ExpressionEngine extension that allows you to control, on a per-weblog basis, where authors land after publishing or updating entries in the ExpressionEngine control panel.

For each weblog you have three redirect location options for both new entries and updated entries:

- Default Preview - EE’s built-in success screen with ugly entry preview
- Publish Form - new entry screen for the same weblog you just published to
- Manage Entries - the Edit tab, filtered to display entries from the weblog you just published to
- 1.0.1 UPDATE: Edit Entry - keep editing the entry you just published or updated

In all cases the author will see a “success” message for their new entry or update, along with the entry’s title and an “Edit this entry” link.

The Extension Settings screen offers optional one-click setting of all of your weblogs to the same option for both new entries and updated entries. (This feature requires that jQuery for the Control Panel be installed loading jQuery 1.3 or newer.)

Entries submitted via SAEFs will be be unaffected by this extension.

Entry REEdirect has been tested on ExpressionEngine 1.6.8.

Download it from GitHub

FF Matrix Bulk/Multiple Upload Addon

2010-03-07T01:45:47-06:00

Here is the beta version of the Matrix Bulk Upload Fieldframe. This fieldframe utilizes jQuery uploadify plugin to provide a visual feedback of all uploads and to allow multiple uploads. The fieldframe then feeds the data into a Fieldframe matrix (1.3.5 tested) to add new rows with the ngen file field OR unieditor tinybrowser(small hack required) of that row prepopulated with one of the newly uploaded files. This feature allows you upload tons of files to a matrix field instead of having to hit browse 100 times.

Directions:

1) Download and place files in appropriate location.
2) Enable the new field type in fieldframe
3) Create a custom field matrix with a ngen file field OR uniedtor tinybrowser field in a column.
4) In this same custom field group add a new field (name it whatever you want, it’s not actually saving a value) and choose FF Matrix Bulk Upload.
5) There are four options to fill out. Choose the field that you defined as a matrix and choose the file upload location (if you are using ngen) that is the same as the one you specified for the ngen file field. Select the column number that your fiel field appears in. Finally select whether this field is an ngen file field or a uniedtor tinybrowser field.
6) Go to edit or publish an entry that has these fields. You will see a browse button that allows you to select multiple files and they will feed into the matrix field when they complete their upload.

Hack Required for Unieditor (Do not change the obfuscate option or this will not work, leave as the standard setting):

Change line 147 of /mx_universal_editor/tinybrowser/config_tinybrowser.php from:

if (basename($_SERVER['PHP_SELF']) == 'style_tinybrowser.css.php' OR basename($_SERVER['PHP_SELF']) == 'tb_tinymce.js.php'){ 

To:

if (basename($_SERVER['PHP_SELF']) == 'style_tinybrowser.css.php' OR basename($_SERVER['PHP_SELF']) == 'tb_tinymce.js.php' OR basename($_SERVER['PHP_SELF']) == 'index.php') { 