bfarber

I'm not clear - you want a "Recent Status Updates" sidebar block that doesn't show the recent status updates?

I just wanted to clarify it's entirely doable as a plugin (we've done it). I should also note the Apple ID integration available out of the box is built on OpenID and could be leveraged as a starting point.

I've logged an internal bug report to have this checked on. Thanks.

This isn't really something we'd "assist" with in a support ticket, other than recommending you do indeed move over to InnoDB. As Paul E. said, phpmyadmin is simply a user interface for generating the raw MySQL query which will be sent behind the scenes. If you are already comfortable generating the raw query, just login to the MySQL console and run it directly. You will avoid timeout possibilities. And indeed, take a backup first.

We have a login module internally that supports OpenID. It may or may not make its way into the core software release at some point.

Optimizing a server is a huge task and it's hard to give a lot of general "do this" recommendations. Most suggestions are specific to an environment. For starters, I'd make sure that (1) you don't have things installed and running that you don't need. The less PHP modules, Apache/nginx modules and so on that are executing, the better off you'll be. And (2) make sure your configurations for Apache/nginx, PHP and MySQL are as optimal as can be. There are thousands of tutorials online that can help you determine what the optimal configuration for your environment and level of traffic should be, and I'd start with reviewing some of those. Basic things like ensuring static files are cached can go a long ways.

This is not possible just yet, but it's been raised internally as a suggestion.

Yes, I don't believe that error is related to the patch.

Patches are released for critical issues. A "Deprecation" notice is not considered a critical issue, so it will be fixed in a maintenance release.

"We have an internal suggestion" means that the idea has been raised and is something we are considering changing in a future release.

I've raised your suggestion internally for further consideration in a future release. Have you been directly impacted by this issue in some way?

1) Convert MyISAM tables to InnoDB 2) Make sure that your MySQL server is tuned for InnoDB. 3) Follow the general recommendations Beyond that, you haven't really clarified - are you sure MySQL is the problem? There are many web server optimizations that can make a huge difference too. Do you use a CDN of any sort, or reverse proxy caching?

That link is opening in a new tab for me

You can do the first parts out of the box easily: an input form where people enter their miles and date. You would then need custom coding to show a summary for each user and a total.

Oh no worries - at least it clears up why I wasn't able to find what you were seeing. Thanks for confirming!

I've logged a bug report to have this behavior checked on. Thanks.

I fixed the DateInterval issue. I can't reproduce or see the first issue however, and my code lines aren't matching up. What do you have on line 1120?

You have to install Redis on the server, then the Redis PHP extension into PHP, and then depending upon your server setup you may need to restart your webserver service (commonly Apache, although there are others). How you do this can vary depending upon the OS you are using and other factors. You shouldn't need to reboot the physical server hardware though.

You are adding an HTML comment around PHP code. The PHP code will still execute in that context, but the result will be inside an HTML comment that the browser will hide. You would need to comment out the PHP code using PHP commenting functionality like {{ /* Don't execute this}} {{ $var = 'x';}} {{ */}}

The API key is an inherent security protection. Restricting to the AWS IP range is an extra layer of security. That's really the only option.

By editing the template you could use a conditional to redirect the button manually.

In short, yes you can look at the folders create under /applications and /plugins to review the code.

No, that behavior has not changed.

If you want to implement protections, you should be able to set up IP address restrictions in Google's developer console as I recall, and then set the IP address/IP address range of your server.

Instead of using "share", just copy the URL from your address bar.