Make WordPress Core

Updates from Jeremy Felt Toggle Comment Threads | Keyboard Shortcuts

  • Jeremy Felt 7:18 pm on October 28, 2015 Permalink |
    Tags: , ,   

    Multisite Focused Changes in 4.4 

    WordPress 4.4 has been a very productive release for multisite. In addition to some exciting new enhancements, we were able to resolve some long standing bugs. Check out the full list of multisite focused changes on Trac if you want even more wonderful reading material. 💖

    Introduce WP_Network

    The $current_site global has been maintaining a stdClass object representing an assumed description of a network since the original merge of WordPress MU with WordPress. With the introduction of WP_Network, we give a network a bit more definition and open up possibilities for working with a network (or networks) in a more sane way.

    Take a look at ms-settings.php if you are using a custom sunrise.php to populate the $current_blog or $current_site globals. We now create a WP_Network object from the existing $current_site if it has been populated elsewhere. This is a backward compatible change, though should be tested wherever your code interacts with $current_site, especially if anything has been done to extend its structure.

    See #31985 for more discussion while this was built.

    Introduce *_network_option functions

    During the introduction of WP_Network, we needed a way to populate network options (stored in wp_sitemeta) for a network other than the current.

    add_network_option(), update_network_option(), get_network_option(), and delete_network_option() are all new functions in 4.4. Each takes the network ID as its first argument, matching the structure of the *_blog_option() functions.

    *_site_option() functions remain as the proper way for working with a current network’s options. These now wrap the new *_network_option() functions and pass the current network’s $wpdb->site_id.

    In a future release, likely 4.5, we can look at the introduction of network 0 as a way to store global options.

    See #28290 for more discussion.

    New actions and filters

    • before_signup_header fires before the signup header in wp-signup.php. #17630
    • ms_network_not_found fires when the $current_site global has not been filled and ms_not_installed() is about to fire. #31702
    • invite_user fires immediately after a user is invited to join a site, but before the notification is sent. #33008

    Other enhancements of note:

    • WordPress has always enforced a /blog prefix for the main site’s permalink structure to avoid collisions with other sites in a subdirectory configuration. This was always changeable in the network admin, though the permalinks UI in the site admin never reflected the change and could cause confusion. Now, thanks to #12002, WordPress forgets that /blog was ever assigned if it is changed in the network admin to anything else. When changing this value, choose something that won’t conflict.
    • manage_network_users is now used to determine edit_users caps rather than is_super_admin. In preparation for 4.4, take a look at how you’re using the manage_network_users capability in your code to be sure access is set as intended. #16860
    • Network activated plugins are now visible as “network activated” in an individual site admin if the user can manage network plugins. These are not shown to site administrators. #20104
    • Recently active plugins are now displayed as such in the network admin. #20468
    • Language selection is now available when adding a new site through the network admin. 🌍 #33528
    • Language selection is also now available when signing up for a new site through wp-signup.php. 🌏 #33844
    • Network user searching has been improved by wrapping search terms in asterisk for looser matching. #32913

    Bugs of note fixed:

    • It was previously impossible to set the upload limit for an individual site to 0 as it would then fallback to the default of 100MB. In 4.4, 0 is a respected number. #34037
    • When a site’s home, siteurl, or page_on_front option was updated in the network admin, rewrite rules were previously flushed incorrectly, causing rewrite rules for the main site on the network to take the place of the rewrite rules for the site being changed. #33816
    • Subdirectory sites created on an HTTPS network are now set to HTTPS rather than the incorrect HTTP. 🔒 #33620
    • A site’s title can now be longer than 50 characters! #33973

    Deprecated functions:

    Both get_admin_users_for_domain() #34122 and create_empty_blog() #34120 have never been used by WordPress core and are now deprecated. 🍻

  • Jeremy Felt 5:07 pm on October 14, 2015 Permalink |

    Multisite Office Hours Recap (October 13, 2015) 

    Multisite office hours are held every Tuesday at 20:00 UTC in #core-multisite. The next will be 2015-10-20 2000.

    Today’s chat log
    Overall 4.4 Release Objectives

    Rough ticket agenda posted before the meeting:

    • #28290_network_option() is in trunk with the new parameter order. Is there anything else we should do on this ticket? I’m thinking global options stored as network id 0 should be a new ticket.
    • #31985WP_Network() – Thoughts on making properties private and adding getters? I’m okay with leaving them public, though there’s no turning back. :)
    • #34065 – How often is the network setup screen used to create a new network with another user as the network admin? Should we just bail early with a message or think about refactoring this?
    • #20104 – Marked as commit, toss thoughts in now if you haven’t… :)
    • #34287 – Value of a “Settings” link under the Network Admin menu?
    • Open floor


    • #28290
      • Where does _network_option() belong? It has to stay in options.php because we wrap with _site_option() now. Moving to a new ms-options.php or similar would mean including that file anyway during single site load.
      • Are we leaving anything on the table? Requesting comments on this one. We’re happy with _network_option() as it is and happy including to have it in core. Does anyone have concerns with the current state?
      • We’ll want to close this ticket pre-beta (one week), so leave your comments! :)
    • #31985WP_Network(). We seem okay here. Going to stick with public properties to meet general assumptions and to avoid back-compat errors with the existing $current_site. We can bring up additional enhancements in new tickets. Ticket closed as fixed.
    • #34065 – This opened a larger can of worms around what “network admin email” means in #34293. In the meantime, we can address this ticket with a few assumptions. Added note to ticket.
    • #20104 – Everybody is happy. Ticket committed. Those who can manage network plugins now see the status of those network plugins in the site admin.
    • #34287 – We had a collective +1 on adding “Settings” to the Network Admin menu. Ticket committed.
    • #34293New ticket. @ipstenu updated with some conclusions and clarifications so we can keep the discussion going. We should update messaging around the several different types of emails used to send or receive notifications in multisite.

    Thanks everyone!

  • Jeremy Felt 5:49 pm on October 7, 2015 Permalink |

    Multisite Office Hours Recap (October 6, 2015) 

    Multisite office hours are held every Tuesday at 20:00 UTC in #core-multisite. The next will be 2015-10-13 2000.

    Today’s chat log
    Overall 4.4 Release Objectives

    This was our first structured office hours in a bit after a lag, but here’s to being back in action. :)

    A rough agenda posted before the meeting:

    • #28290 – We’ve added _network_option() and need to converse some more about parameter order. After some thoughts shared in Slack yesterday, it seems that having $network_id first makes sense. This would have the side effect of a seamless transition for those already using the functions in WP Multi Network. We should also add global options with a network ID of 0. This may belong in another ticket.
    • #18292 – Opinions on whether we should temporarily fix the network upgrade process by halting on a failed site rather than using wp_die() and killing the entire thing. A long term solution via #11869 is to revamp the process entirely so that we don’t have to worry about silly things like this.
    • #34145 – Does anyone have a problem with removing Lucida Grande from wp-activate.php?
    • #31240 – Patch needed, I haven’t had time to work on it yet, though I think we still have time in this cycle.
    • #32450 – More testing, iterations on the current patch needed. This one is likely tougher than WP_Network as it touches more parts of core once implemented.
    • Open floor, other things, tickets, etc…


    • #28290 – Go with a new parameter order and accept $network_id first in _network_option(). Revert the change to use _network_option() in core. Open a new ticket to talk about storing network ID 0 as a global option. Initial revert in [34912].
    • #18292 – Let’s wait on the halt behavior and stick with what we know. We should tackle #11869 as a way to resolve all of this. Ticket closed.
    • #34145 – Get rid of it. Committed in [34882].
    • #31240 – Postpone this until we’ve had a chance to really decide what we want from the Add New site screen. Not all networks are created equal in their configuration of domain and path. We need to start doing some more unit testing around what we actually do and do not support. Ticket moved to future release.
    • #32450 – We didn’t have a chance to cover this one, more testing and iterations needed. :)

    Thanks all!

  • Jeremy Felt 3:37 am on September 17, 2015 Permalink |

    Multisite objectives for the 4.4 cycle 

    We’ve made a good chunk of progress in the 4.4 cycle thus far and are starting to go in a direction that can be better defined through a handful of objectives. Let’s go through them:

    • WP_Network has been comitted to core. This is one of the major objectives for 4.4 and should be tested thoroughly. #31985
    • WP_Site will follow shortly and is another main objective. This still needs some initial work before commit, and should also be tested thoroughly. #32450
    • In the process of implementing WP_Network, it became clear that now is the time to introduce *_network_option() functions as replacements for *_site_option(). This has long been a one day objective, and now that we have an applicable use case in core, we’re going for it. Follow and help with progress in #28290.
    • In 4.3, we combined the domain/path fields when editing a site in both subdirectory and subdomain mode to allow for easier entry and for the beginnings of arbitrary domain/path support. To complete this, we need to follow up when adding a site if a subdomain install. Subdirectory configurations will remain the same. #31240
    • Adding a field for scheme to the wp_blogs table is still on the table in #14172. This goes hand in hand with the work being done by the HTTP/2 group and could help clear the way for quite a few other HTTPS tickets.
    • WP_Site_Query and WP_Network_Query are probably long shots for 4.4, and may need to wait until 4.5. That said, if progress is made on either in the near future, then we can start to speed that up.

    As we introduce things like WP_Network and WP_Site, we’re going to continue seeing smaller places that can be cleaned up or fixed in a different way. Keep your eyes open for those opportunities. And as always, if you have a ticket you’d like to see through and it’s not on this page, chime in early and let’s get it done.

    Multisite office hours are on Tuesdays at 20:00UTC in #core-multisite. We’ll be discussing these objectives weekly, and the channel is always open. :)


  • Jeremy Felt 6:14 am on July 24, 2015 Permalink
    Tags: , ,   

    Multisite Focused Changes in 4.3 

    Howdy! We’ve made quite a bit of progress in multisite as part of the 4.3 cycle and have a bunch slated to continue working on throughout the year. If you’d like to follow along, stop by our weekly office hours on Tuesdays at 20:00 UTC in #core-multisite.

    Here’s what we have coming in 4.3…

    Begin streamlining the interface for setting a site’s URL.

    Editing a site’s address for what it is—a combination of domain and path—becomes more straightforward in 4.3. A full address with or without scheme can now be entered if multisite is configured as subdomain. Network administrators have been hacking at this anyway for years when the two fields were separate to provide arbitrary domain support. See #22383 for all the details.

    In combination with this, the checkbox for “Update siteurl and home as well” has been removed when editing a site. Instead we can make an educated decision based on the current state. If the home and/or siteurl domain and path match the existing domain and path of the site, we assume that we can update all values with the new information. See #32503 for details.

    And to better enforce URLs vs domain and path, we’ve improved the default columns displayed in MS Sites List Table. The full URL is now show instead of the domain or the path. We also now show a total user count for each site rather than the first 5 users. See #32434 for details.

    Introduce get_main_network_id()

    This likely isn’t too useful to many, though will come in handy for those working with custom multi-network configurations. It will always return 1 on single site or if the current network has an ID of 1. It will return PRIMARY_NETWORK_ID if defined. And if those conditions aren’t met, it will go to the database to determine which ID is the first in line.

    It is possible to filter this value with the new get_main_network_id filter for those who have multiple networks and would like to avoid the incremental assumptions. See #30294 for the details.

    Visual and interface enhancements:

    • Better responsive styling for my-sites.php, a screen that would love to have a complete overhaul one day but now looks much better on smaller devices. #31685
    • Also in my-sites.php, the Save Changes button is conditionally displayed only if the user is a member of more than one site OR if a plugin or theme has filtered the HTML on this screen and may be expecting a Save Changes button to exist. #32645
    • Achieve parity between single and multisite by removing the Upgrades subsection in the menu and moving Updates to Dashboard. #32431
    • Provide a link to the dashboard when editing a site in the network admin. Previously, only the URL would show in the title area of the site screens with no great way to access the dashboard. Now, the full site name is shown as the title and smaller text URLs are displayed underneath for Visit and Dashboard. #32525
    • Mobile display of the network admin has been improved in general. A few inputs have been adjusted on mobile to make them act as expected. #32643, #32644, #32646. A full sweep of “content overruns” was done to ensure admin screens don’t overflow the screen on small mobile devices. #32846, #32962.

    Bugs of note fixed:

    • Don’t allow usernames over 60 characters long, a limit that was already in place via the database schema but was not enforced explicitly in code. #26784
    • Calculate the storage space used correctly for the main site. Previously, it was possible that the main site would reach it’s calculated space limit because the storage of all other sites was included in the total. #30202
    • get_blogs_of_user() now returns proper values for the archived, spam, and deleted properties. These were previously forced to 0 only when using this function. #32281
    • Deleting a super admin user via wpmu_delete_user() is no longer possible. This matches the expectation previously set by the UI. #32935

    And because some are smaller and were left out of the above, here’s a full list of multisite focused changes made in 4.3.

  • Jeremy Felt 4:47 pm on June 24, 2015 Permalink

    Multisite Office Hours Recap (June 23, 2015) 

    Multisite office hours are held every Tuesday at 20:00 UTC in #core-multisite.

    Today’s chat log
    Overall 4.3 Release Objectives

    Last week’s (and this week’s) objectives:

    • More flow, more tickets, more observations to aid with Network Admin UI improvement.
    • Get a good patch up for #31240, possible commit.
    • Ongoing iterations, progress, discussion on `WP_Network` and `WP_Site` (and friends).
    • Write post, generate discussion around HTTPS in multisite for real (lower priority).

    It was a super light weight week for multisite, so not much progress. There was some traffic on existing tickets, but not much new activity. Summer lull… 🌞

    @hugobaeta gathered a few UI/UX tickets for WCEU contributor day – #32525, #32645, and #32647. We also have the general Admin UI screen sweep spreadsheet. Another ticket in that vein via @johnjamesjacoby is #32754, which is a string change but goes along with UX.

    If anyone has other UI/UX tickets, please make note. I’ll be poking around on Saturday. For anyone attending WCEU contributor day, a server with multisite is available for you to test on. I’ll hook some others up with super admin access beforehand.

  • Jeremy Felt 9:20 pm on June 16, 2015 Permalink

    Multisite Office Hours Recap (June 16, 2015) 

    Multisite office hours are held every Tuesday at 20:00 UTC in #core-multisite.

    Today’s chat log
    Overall 4.3 Release Objectives

    Last week’s objectives:

    • New tickets to address found issues in flow. These issues logged in the screen sweep spreadsheet.
    • Iterations on `WP_Site` and `WP_Network`. Discussion around iterations.
    • #22383 and #32503 committed.
    • Write post, generate discussion around HTTPS in multisite.

    Today’s meeting agenda:

    • Progress on capturing, observing, ticketing flows.
    • Next steps to combined domain/path UI – Add New site flow #31240
    • `WP_Network`, `WP_Site` progress – @jjj
    • Open floor for tickets, thoughts, etc…

    Topic Details:

    Progress on capturing, observing, ticket flows:

    Tickets #32647, #32645, #32643, #32644
    chat log

    • @earnjam added iPad flows.
    • @sharonaustin captured a bunch of flow data/notes and will be posting it to Make/Flow soon.
    • Some great progress was made over the weekend during the WCPHL contributor day. #32643 was opened and committed as an example of the process. #32644, #32645, #32646, and #32647 were also opened.
    • @earnjam is going to take the lead on getting #32647 and #32645 ready for next week as part of a My Sites overhaul.
    • The bugs from #32643, #32644, and #32646 are likely found in other places throughout core as well.
    • We should collaborate on a flow/design/admin ui/network admin ui contributor doc for WCEU with some basic “here’s what we need” guidelines. @helen @boren @sheri

    Objectives for next week: #32645, #32647 committed. More flow, more tickets, more observations. :)

    Next steps to combined domain/path UI

    Tickets: #31240, #22383, #32434, #32503
    chat log

    • #22383, #32434, #32503 are all committed and closed. 👍
    • Originally #31240 seemed kind of off the table for 4.3, but it seems very possible now. @jeremyfelt will take a shot at getting that prepped for next week.
    • Once these are both in, we should start having some validation questions pretty soon.

    Objective for next week: Patch and/or commit for #31240.

    Progress on `WP_Network`, `WP_Site`

    Tickets: #31985, #32450, #32504, #31148
    chat log

    • @earnjam is going to open a ticket to track `WP_Site_Query` and take a stab at that.
    • We need to iterate some more on the other existing patches.
    • Completely comfortable with progress on this continuing through 4.3 for a target of 4.4 early. It would also be nice just to get it in now. :)

    Objective for next week: Iterations, progress, discussion.

    Other items:

    • @jeremyfelt owes an HTTPS in multisite post still. Maybe by tomorrow?
    • No other items. A pretty quiet chat today.

    See you next week!

  • Jeremy Felt 3:50 pm on June 12, 2015 Permalink
    Tags: contributor day,   

    How you can help with the Network Admin UI during contributor day 

    A previous write-up explains how you can help test and capture the network admin UI. Here’s a specific version for how you can help during contributor day this weekend.

    There are four steps to the workflow at the moment:

    1. Capture a visual record of network admin screens.
      • Ideally on a device/browser combination that has not yet been captured.
      • If comfortable, post the screen captures and notes on make.wordpress.org/flow.
      • If you need access to Make/Flow, ask in #core-flow on Slack or around the physical room you’re in (if it’s full of contributors).
    2. Observe screens, actions, and results throughout the network admin.
      • This can happen during or after step 1. You can also just do this without the first step.
      • Look for things that don’t make sense, visual errors, pieces that are difficult on mobile, etc…
    3. Document observations in the screen sweep sheet.
      • This can be with or without a Trac ticket. With or without a screenshot.
      • Acts as a note so that we know that to come back to as part of the overall admin UI improvement effort.
    4. Help with the screen sweep sheet.
      • Open a ticket if there is none. Add screenshots if there are none. Confirm/deny the issue.
      • And patch. If there’s a ticket on the screen sweep sheet that you can patch, submit away.

    While this is an ordered list, you do not need to treat it like one. Pick a step that feels comfortable and concentrate on that. If you need guidance, there are folks in Slack that are always happy to help.

    Current captured visual records:

    By all means, if you have a device that is already captured, don’t hesitate to capture it in your own way or to skip step 1 entirely and start observing.

    Thanks for the help!

    • Saravanan 2:57 am on June 13, 2015 Permalink | Log in to Reply

      I would like to help out with this. I will need access to sites to test them on my iPhone 6 plus; and Mac. Thanks.

  • Jeremy Felt 10:07 pm on June 9, 2015 Permalink

    Multisite Office Hours Recap (June 9, 2015) 

    Multisite office hours are held every Tuesday at 20:00 UTC in #core-multisite.

    Today’s chat log
    Overall 4.3 Release Objectives

    Last week’s objectives:

    • Have all 3 of these tickets closed and committed. #22383, #32434, #32503
    • Additional iterations on `WP_Network` and `WP_Network_Query`.
    • Generate discussion around HTTPS on #14172. @jeremyfelt will gather a list of HTTPS related tickets.
    • Nexus and iPad flows. Tickets created for bugs found in existing flows. Volunteers needed! :)

    Today’s meeting agenda:

    • Status on additional flows/visual records and next steps toward ticket creation.
    • New thoughts/discussion on `WP_Network`, `WP_Site` and friends?
    • Status of #22383, #32434, and #32503
    • Open floor for tickets, thoughts, etc…

    Topic Details:

    Status on additional flows/visual records. Next steps toward ticket creation.

    chat log

    We have new flows captured. @kraftbj posted the Nexus 6 results and @earnjam will be posting iPad shots within the next couple days. @topdown volunteered to capture screens for Samsung Note 8 and possibly other devices as well.

    To date, our device list includes: Nexus 6, iPhone 5s, iPhone 6, and Desktop, with additional screens specific to network upgrade.

    We posted some info late last week on how someone could help test and capture the network admin UI. Test installations of multisite are available for anyone to use if you have a device but just have no way of accessing a multisite installation. Please leave a comment on the post or in #core-multisite if you’d like to get started.

    As we create tickets and find bugs, we need to populate this spreadsheet as part of the overall screen sweep effort.

    Objective for next week: New tickets to address found issues. These issues logged in the screen sweep spreadsheet.

    New thoughts/discussion on `WP_Network`, `WP_Site`, and friends?

    Tickets: #31985, #32450, #32504, #31148
    chat log

    Not much discussion here. @johnjamesjacoby is going to have iterations of `WP_Site` and `WP_Network` this week. We should have a chat in #core-multisite soon after.

    Objective for next week: Iterations on `WP_Site` and `WP_Network`. Discussion around iterations.

    Status of #22383, #32434, and #32503

    Tickets: #22383, #32434, #32503
    chat log

    Objective for next week: Let’s cross our fingers that these are closed by tomorrow.

    Other items:

    Tickets: #14172, #32602
    chat log

    • @jeremyfelt still needs to generate discussion around HTTPS for #14172
    • @ipstenu found an issue with the plugin details modal when viewing plugin details on a sub site that has a different domain/scheme from the network admin. The switch to `network_admin_url()` that causes this came in #17902. A new ticket #32602 is open.

    Thanks everyone!

  • Jeremy Felt 7:24 am on June 5, 2015 Permalink
    Tags: , ,   

    Help Test and Capture the Network Admin UI 

    One of the wider objectives of WordPress 4.3 is to improve on the Network Admin UI. This includes refining the experience on different device sizes. We first need to capture a baseline of existing screen flows and identify tickets from that.

    We need help capturing this data. :)

    Having access to a local, multisite WordPress installation is the preferred method, as you’ll have an easier time making changes, applying patches, and generally having control over the data. Here are some guidelines for testing locally:

    Realizing that installing and configuring multisite locally can be a barrier, a test server is available for anyone to access. This test server has two network installations, one for subdirectory and another for subdomain. Data will be reset on a regular basis. This allows anyone to go through the various network admin tasks.

    Both networks are running trunk as of about 20 minutes ago. I’ll be making an effort to automate the maintenance of that setup.

    If you’d like a super admin account to these networks, leave a comment below or ping @jeremyfelt anywhere. #core-multisite is preferred. I’ll create a matching username to your wordpress.org profile name and set you loose to capture and break things at will. :)

    Once you have a test network available, here are the things we need captured:

    • Add a new user to a site when the user does not currently exist as a network user.
    • Add a new user to a site when the user does exist as a network user.
    • Install, enable, and then activate a theme for a single site on the network.
    • Install a theme and enable it for use on a network.
    • Install and then activate a plugin for use on a single site on the network.
    • Install and then network activate a plugin.
    • Create a new site on the network.
    • Update a plugin.
    • Update a theme.
    • Edit the domain/path for an existing site on the network.

    Once captured, it’s great to share all of the data on the Make/Flow site, with a description of the screens tested and the device/browser configuration. If you need access to Make/Flow to post your results, leave a comment here or in #core-flow.

    Specific details on each of these screens should also be added to this spreadsheet that the overall Admin UI team is using to coordinate efforts. Feel free to capture one workflow or many.

    If you notice a bug in the screens you have captured, or in the screens captured by somebody else, it should be reported. Ask in #core-multisite or #core-flow on Slack if you need any help.

    • crplz 10:02 am on June 5, 2015 Permalink | Log in to Reply

      would love to contribute in this as almost 100% of the sites we manage are Multi-Site enabled. Have tons of experience facing problems managing several wp networks loaded with users/cpt/etc.

      Can I get a super admin account? #core-multisite

      • Jeremy Felt 6:31 pm on June 5, 2015 Permalink | Log in to Reply

        Great! You should have two emails with account information for the networks sent to the email used to leave this comment.

    • Sharon Austin 12:10 pm on June 5, 2015 Permalink | Log in to Reply

      I would love to be able to help out with this….as much as for some guidance on “how” to do a proper test as for any other aspect! Thank you for creating the opportunity!

      • Sharon Austin 5:31 pm on June 5, 2015 Permalink | Log in to Reply

        Sorry, not sure if I needed to be more specific in my request above. I would like a super admin account for user: sharonaustin for testing Network 1 and Network 2. Thanks again for doing this.

        • Jeremy Felt 6:32 pm on June 5, 2015 Permalink | Log in to Reply

          Thank you! You should have two emails with account information for the networks sent to the address used to leave this comment.

    • Ben Hansen (ubernaut) 2:53 pm on June 6, 2015 Permalink | Log in to Reply

      you should add checking out the user list to that list :)

    • Sharon Austin 6:19 pm on June 9, 2015 Permalink | Log in to Reply

      @jeremyfelt Thank you, got ’em. While I’ll go in right away, I may be quiet for a few days to lurk, watch, and make sure I understand what you’re looking for…I want to give feedback that is well-targeted to the needs. Thanks again for doing this.
      @ubernaut recommendation so noted! :-)

    • Sharon Austin 8:55 pm on June 11, 2015 Permalink | Log in to Reply

      @jeremyfelt I have sent you email with the first summary (Subdirectory) to your gmail account. If you wouldn’t care to look it over before I post, that would be a favor. Feel free to share it if you think it is okay to share. I’ll work on the Subdomain tomorrow.

      Thanks again for doing this.

    • Sharon Austin 4:58 pm on June 12, 2015 Permalink | Log in to Reply

      Apologies, @jeremyfelt, I just read the latest post sent out about testing the UI…I will put the screenshots on #makeflow, Thanks again.

    • Saravanan 8:03 am on June 20, 2015 Permalink | Log in to Reply

      @jeremyfelt, I would like to help out with this. I will need access to sites to test them on my iPhone 6 plus; and Mac. Thanks.

compose new post
next post/next comment
previous post/previous comment
show/hide comments
go to top
go to login
show/hide help
shift + esc
Skip to toolbar